[GH-ISSUE #2440] Unable to delete identity provider #6964

Closed
opened 2026-04-25 15:57:19 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @buggystick on GitHub (Feb 9, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2440

Describe the Bug

I'm wanting to delete an identity provider I no longer want. At first when I tried to delete it, I got "an error occured" message. Thinking this might because I had a user associated with the provider, I then tried to delete that user. However, I got the same "an error occured" message. Docker logs show the following:

pangolin | 2026-02-09T17:47:28+00:00 [error]: FOREIGN KEY constraint failed
pangolin | Stack: SqliteError: FOREIGN KEY constraint failed
pangolin | at PreparedQuery.run (file:///app/node_modules/drizzle-orm/better-sqlite3/session.js:72:22)
pangolin | at QueryPromise.resultCb (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:119:64)
pangolin | at QueryPromise.execute (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:13:17)
pangolin | at QueryPromise.then (file:///app/node_modules/drizzle-orm/query-promise.js:21:17)
pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {"code":"SQLITE_CONSTRAINT_FOREIGNKEY"}

Environment

  • OS Type & Version: Fedora 42
  • Pangolin Version: EE 1.15.2
  • Gerbil Version: 1.3.0
  • Traefik Version: 3.6.7
  • Newt Version: 1.8.1
  • Olm Version: (if applicable) N/A

To Reproduce

  1. Create an Identity provider (possibly also add user with said provider)
  2. Delete provider

Expected Behavior

Identity Provider and all associated users are deleted.

Originally created by @buggystick on GitHub (Feb 9, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2440 ### Describe the Bug I'm wanting to delete an identity provider I no longer want. At first when I tried to delete it, I got "an error occured" message. Thinking this might because I had a user associated with the provider, I then tried to delete that user. However, I got the same "an error occured" message. Docker logs show the following: pangolin | 2026-02-09T17:47:28+00:00 [error]: FOREIGN KEY constraint failed pangolin | Stack: SqliteError: FOREIGN KEY constraint failed pangolin | at PreparedQuery.run (file:///app/node_modules/drizzle-orm/better-sqlite3/session.js:72:22) pangolin | at QueryPromise.resultCb (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:119:64) pangolin | at QueryPromise.execute (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:13:17) pangolin | at QueryPromise.then (file:///app/node_modules/drizzle-orm/query-promise.js:21:17) pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {"code":"SQLITE_CONSTRAINT_FOREIGNKEY"} ### Environment - OS Type & Version: Fedora 42 - Pangolin Version: EE 1.15.2 - Gerbil Version: 1.3.0 - Traefik Version: 3.6.7 - Newt Version: 1.8.1 - Olm Version: (if applicable) N/A ### To Reproduce 1) Create an Identity provider (possibly also add user with said provider) 2) Delete provider ### Expected Behavior Identity Provider and all associated users are deleted.
GiteaMirror added the stale label 2026-04-25 15:57:19 -05:00
Author
Owner

@buggystick commented on GitHub (Feb 9, 2026):

Ahh... I figured out a workaround. I forgot that the user is also associated with an organization. I would have expected deleting the identity provider would cascade the deletion of organization/server users

  1. Delete the user from the organization
  2. Delete the user from the server
  3. Delete the identity provider
<!-- gh-comment-id:3873129775 --> @buggystick commented on GitHub (Feb 9, 2026): Ahh... I figured out a workaround. I forgot that the user is also associated with an organization. I would have expected deleting the identity provider would cascade the deletion of organization/server users 1) Delete the user from the organization 2) Delete the user from the server 3) Delete the identity provider
Author
Owner

@github-actions[bot] commented on GitHub (Feb 24, 2026):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3948172100 --> @github-actions[bot] commented on GitHub (Feb 24, 2026): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
Author
Owner

@miloschwartz commented on GitHub (Feb 25, 2026):

Unfortunately I was unable to reproduce this. I created an IDP, associated a user, and was able to delete the IDP from the UI cleanly. Am I missing a step?

<!-- gh-comment-id:3961858471 --> @miloschwartz commented on GitHub (Feb 25, 2026): Unfortunately I was unable to reproduce this. I created an IDP, associated a user, and was able to delete the IDP from the UI cleanly. Am I missing a step?
Author
Owner

@github-actions[bot] commented on GitHub (Mar 13, 2026):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:4051342205 --> @github-actions[bot] commented on GitHub (Mar 13, 2026): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 27, 2026):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:4139240928 --> @github-actions[bot] commented on GitHub (Mar 27, 2026): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#6964