Originally created by @tim-van-dijkhuizen on GitHub (Sep 25, 2025).
Originally assigned to: @miloschwartz on GitHub.
I have configured an IDP using Keycloak, enabled "Auto Provision Users" and created an organization policy that assigns roles based on the groups claim supplied by Keycloak. Then I enabled "Use Platform SSO" for a resource, allowed access to my Roles and enabled "Auto Login with External IDP".
When logging in with a user that has the right permissions it all works fine no problem. But when a user that does not have the required role tries to login they get stuck in a (seemingly) endless loop of:
Accessing resource exposed by Pangolin
Being redirected to the IDP and logging in, then back to Pangolin
Pangolin refuses the user and redirects back to the IDP
The IDP is already logged in and instantly redirects the user back to Pangolin
The cycle continues
Am I doing something wrong, or is this a bug? Would be great if Pangolin showed an access denied page.
Software info:
Pangolin: v1.9.4
Newt: 1.5.0
I probably should update but looking at the changelog this issue has not been resolved yet.
Originally created by @tim-van-dijkhuizen on GitHub (Sep 25, 2025).
Originally assigned to: @miloschwartz on GitHub.
I have configured an IDP using Keycloak, enabled "Auto Provision Users" and created an organization policy that assigns roles based on the groups claim supplied by Keycloak. Then I enabled "Use Platform SSO" for a resource, allowed access to my Roles and enabled "Auto Login with External IDP".
When logging in with a user that has the right permissions it all works fine no problem. But when a user that does not have the required role tries to login they get stuck in a (seemingly) endless loop of:
1. Accessing resource exposed by Pangolin
2. Being redirected to the IDP and logging in, then back to Pangolin
3. Pangolin refuses the user and redirects back to the IDP
4. The IDP is already logged in and instantly redirects the user back to Pangolin
5. The cycle continues
Am I doing something wrong, or is this a bug? Would be great if Pangolin showed an access denied page.
**Software info:**
Pangolin: v1.9.4
Newt: 1.5.0
I probably should update but looking at the changelog this issue has not been resolved yet.
I've figured out why mine was looping. Seems that Pangolin isnt adding the autoprovisioned users to the correct org. Pangolin was putting the Authentik users into a competly differet userspace separate from any org.
I saw that Pangolin was giving the autoprovisioned users a Username that was a long string i.e. "250029b692de7ff504cfe7f435c8223013c64eacefd25ce8fe1fafa1c77f740e". I had to then take this string from "All Users" and is as the username in the org users for it to work. It would then convert the sting to the proper username.
@RJDavison commented on GitHub (Sep 29, 2025):
I've figured out why mine was looping. Seems that Pangolin isnt adding the autoprovisioned users to the correct org. Pangolin was putting the Authentik users into a competly differet userspace separate from any org.
I saw that Pangolin was giving the autoprovisioned users a Username that was a long string i.e. "250029b692de7ff504cfe7f435c8223013c64eacefd25ce8fe1fafa1c77f740e". I had to then take this string from "All Users" and is as the username in the org users for it to work. It would then convert the sting to the proper username.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tim-van-dijkhuizen on GitHub (Sep 25, 2025).
Originally assigned to: @miloschwartz on GitHub.
I have configured an IDP using Keycloak, enabled "Auto Provision Users" and created an organization policy that assigns roles based on the groups claim supplied by Keycloak. Then I enabled "Use Platform SSO" for a resource, allowed access to my Roles and enabled "Auto Login with External IDP".
When logging in with a user that has the right permissions it all works fine no problem. But when a user that does not have the required role tries to login they get stuck in a (seemingly) endless loop of:
Am I doing something wrong, or is this a bug? Would be great if Pangolin showed an access denied page.
Software info:
Pangolin: v1.9.4
Newt: 1.5.0
I probably should update but looking at the changelog this issue has not been resolved yet.
@juanbstevens commented on GitHub (Sep 27, 2025):
I just came across this same issue today.
@miloschwartz commented on GitHub (Sep 27, 2025):
Looking into this!
@keonramses commented on GitHub (Sep 28, 2025):
Thank you for looking into this Milo.
@RJDavison commented on GitHub (Sep 29, 2025):
Same problem with Authentik
@RJDavison commented on GitHub (Sep 29, 2025):
I've figured out why mine was looping. Seems that Pangolin isnt adding the autoprovisioned users to the correct org. Pangolin was putting the Authentik users into a competly differet userspace separate from any org.
I saw that Pangolin was giving the autoprovisioned users a Username that was a long string i.e. "250029b692de7ff504cfe7f435c8223013c64eacefd25ce8fe1fafa1c77f740e". I had to then take this string from "All Users" and is as the username in the org users for it to work. It would then convert the sting to the proper username.
@miloschwartz commented on GitHub (Oct 8, 2025):
Thanks everyone! I believe I fixed this problem and the fix will be released soon in 1.11.