mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-06 12:55:03 -05:00
[GH-ISSUE #1381] Cant delete user from pangolin that was created using OIDC via Authentik #1884
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#1884
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sudoicezen on GitHub (Aug 29, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1381
I'm toying around with setting up OIDC and have been able to get authentik to work to some extent but have not been able to get auto provision users to work just yet.
Several times ive logged in using authentik and several times ive had to delete the user so that I could try again.
The situation now is when I go delete the user it asks me to type in that users "name" which in this case is a long string of alpha numeric characters and it keeps stating that its incorrect.
Shy of redeploying im not sure what to do here.
@MarlosChida commented on GitHub (Aug 29, 2025):
I am using Entra ID set using OIDC and It just works fine. When I want to delete a user, I can just type the user's e-mail and It works.
I also have Group Role Mapping from the OIDC provider and It works perfect.
Can you post your settings?
@miloschwartz commented on GitHub (Sep 27, 2025):
Not able to reproduce. You should be able to copy the name in the modal into the input box as confirmation. Is this in the server admin UI or the org users UI?
@RJDavison commented on GitHub (Oct 2, 2025):
I'm getting the same problem trying to delete an Autoprovisioned user through Authentik. The username string cant be used to delete the user.
The user in question wasnt given a name by pangolin so I added the user again and it worked but now im left with this entity that I cant delete
If I dete the user with the allocated name, the unamed one still remains.
@sudoicezen commented on GitHub (Oct 2, 2025):
This was my exact issue. I gave up on this config for a couple of reasons though. For starters I couldn't get users to auto prevision. The other is I really didn't need any other users to access sites where I had pangolin set to require authentication via pangolin so it would be a waste of time for my use case.
@RJDavison commented on GitHub (Oct 2, 2025):
I feel your frustration. I'm not sure if this feature is broken as the only way I can get Authentik autoprovisioned users added (through lots of trial and error) was to copy the user string for the autoprovisioned user from Server Admin =>> users into the Org users. It would then allow me to log in using Authentik. If I didnt do this then the autoprovisioned users were not being added to an org and logging in with their credentials would lead to a continious boot loop. There is a similar bug open where this loop is occuring.
Great software but it seems a very convoluted way of adding users if this is the intended action!
@github-actions[bot] commented on GitHub (Oct 17, 2025):
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.
@RJDavison commented on GitHub (Oct 17, 2025):
So ive just upgraded to 1.11.0 in a hope that autoprovisioning with Authentik works - but alas no.
I add an authentik user to pangolin and then try and log in with that user through Authentik and then it gives me this....
@miloschwartz commented on GitHub (Oct 17, 2025):
@RJDavison Do you have a policy created in the IDP settings? When you enable auto provision, you still need to set a policy to ensure the user gets mapped to the correct organization / roles.
@RJDavison commented on GitHub (Oct 17, 2025):
@miloschwartz My bad. Apologies. I had some syntax errors in the IDP policy. Now sorted and working. Thank you.
@github-actions[bot] commented on GitHub (Nov 1, 2025):
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.
@github-actions[bot] commented on GitHub (Nov 16, 2025):
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.