OIDC User being removed from Organisation #348

Open
opened 2025-11-13 11:57:33 -06:00 by GiteaMirror · 18 comments
Owner

Originally created by @joshdinsdale on GitHub (May 16, 2025).

Originally assigned to: @miloschwartz on GitHub.

Added my Pocket ID admin user to Pangolin and set it to have the Admin role.

Open an incognito browser tab and connect to one of my proxied resources that is Uprotected in Pangolin and uses OIDC to auth directly with pocket touch. I am redirected to Pocket Touch, login and amsucesfully redirected to the resource.
I open another tab, and connect to a Protected resource, i get the Pangolin login page and choose the pocket id login option, i am already authed but am then told by Pangolin that i do not have access.

In my other browser logged into Pangolin as admin, i browse to users for the resource and find that my pocket id user no longer shows in the user list. If i go to Server Admin I can see the users in the list here.

Some mechanism in Pangolin is removing this user from the site.

Originally created by @joshdinsdale on GitHub (May 16, 2025). Originally assigned to: @miloschwartz on GitHub. Added my Pocket ID admin user to Pangolin and set it to have the Admin role. Open an incognito browser tab and connect to one of my proxied resources that is Uprotected in Pangolin and uses OIDC to auth directly with pocket touch. I am redirected to Pocket Touch, login and amsucesfully redirected to the resource. I open another tab, and connect to a Protected resource, i get the Pangolin login page and choose the pocket id login option, i am already authed but am then told by Pangolin that i do not have access. In my other browser logged into Pangolin as admin, i browse to users for the resource and find that my pocket id user no longer shows in the user list. If i go to Server Admin I can see the users in the list here. Some mechanism in Pangolin is removing this user from the site.
GiteaMirror added the needs investigating label 2025-11-13 11:57:33 -06:00
Author
Owner

@jhedfors commented on GitHub (May 16, 2025):

I am having the exact same thing happening using Google identity provider.

https://www.reddit.com/r/PangolinReverseProxy/comments/1klunp7/access_denied/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Image

I also posted my issue on the Discord support channel.

@jhedfors commented on GitHub (May 16, 2025): I am having the exact same thing happening using Google identity provider. https://www.reddit.com/r/PangolinReverseProxy/comments/1klunp7/access_denied/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button ![Image](https://github.com/user-attachments/assets/9e5e87be-8fe8-4272-809d-1e0855a27fe0) I also posted my issue on the Discord support channel.
Author
Owner

@joshdinsdale commented on GitHub (May 16, 2025):

I've just confirmed this for another user account on my system byt logging in withe a 1-time link, unprotected resources are fine, but as soon as the user tries to access a protected resource something is removing the account from the organisation.

@joshdinsdale commented on GitHub (May 16, 2025): I've just confirmed this for another user account on my system byt logging in withe a 1-time link, unprotected resources are fine, but as soon as the user tries to access a protected resource something is removing the account from the organisation.
Author
Owner

@jonzey231 commented on GitHub (May 16, 2025):

I'm seeing this intermittently with Google Auth. Seems fine for some users but completely breaks with others even thought they were all setup at the same time the same way.

@jonzey231 commented on GitHub (May 16, 2025): I'm seeing this intermittently with Google Auth. Seems fine for some users but completely breaks with others even thought they were all setup at the same time the same way.
Author
Owner

@jonzey231 commented on GitHub (May 16, 2025):

Added my Pocket ID admin user to Pangolin and set it to have the Admin role.

Open an incognito browser tab and connect to one of my proxied resources that is Uprotected in Pangolin and uses OIDC to auth directly with pocket touch. I am redirected to Pocket Touch, login and amsucesfully redirected to the resource. I open another tab, and connect to a Protected resource, i get the Pangolin login page and choose the pocket id login option, i am already authed but am then told by Pangolin that i do not have access.

In my other browser logged into Pangolin as admin, i browse to users for the resource and find that my pocket id user no longer shows in the user list. If i go to Server Admin I can see the users in the list here.

Some mechanism in Pangolin is removing this user from the site.

Disable Auto provisioning if you're not actively using it to assign roles/orgs. It fixes this issue.

@jonzey231 commented on GitHub (May 16, 2025): > Added my Pocket ID admin user to Pangolin and set it to have the Admin role. > > Open an incognito browser tab and connect to one of my proxied resources that is Uprotected in Pangolin and uses OIDC to auth directly with pocket touch. I am redirected to Pocket Touch, login and amsucesfully redirected to the resource. I open another tab, and connect to a Protected resource, i get the Pangolin login page and choose the pocket id login option, i am already authed but am then told by Pangolin that i do not have access. > > In my other browser logged into Pangolin as admin, i browse to users for the resource and find that my pocket id user no longer shows in the user list. If i go to Server Admin I can see the users in the list here. > > Some mechanism in Pangolin is removing this user from the site. Disable Auto provisioning if you're not actively using it to assign roles/orgs. It fixes this issue.
Author
Owner

@joshdinsdale commented on GitHub (May 16, 2025):

Added my Pocket ID admin user to Pangolin and set it to have the Admin role.
Open an incognito browser tab and connect to one of my proxied resources that is Uprotected in Pangolin and uses OIDC to auth directly with pocket touch. I am redirected to Pocket Touch, login and amsucesfully redirected to the resource. I open another tab, and connect to a Protected resource, i get the Pangolin login page and choose the pocket id login option, i am already authed but am then told by Pangolin that i do not have access.
In my other browser logged into Pangolin as admin, i browse to users for the resource and find that my pocket id user no longer shows in the user list. If i go to Server Admin I can see the users in the list here.
Some mechanism in Pangolin is removing this user from the site.

Disable Auto provisioning if you're not actively using it to assign roles/orgs. It fixes this issue.

This sounds promising, I did turn this on after upgrading. Will disable and visit a try.

Thanks!

@joshdinsdale commented on GitHub (May 16, 2025): > > Added my Pocket ID admin user to Pangolin and set it to have the Admin role. > > Open an incognito browser tab and connect to one of my proxied resources that is Uprotected in Pangolin and uses OIDC to auth directly with pocket touch. I am redirected to Pocket Touch, login and amsucesfully redirected to the resource. I open another tab, and connect to a Protected resource, i get the Pangolin login page and choose the pocket id login option, i am already authed but am then told by Pangolin that i do not have access. > > In my other browser logged into Pangolin as admin, i browse to users for the resource and find that my pocket id user no longer shows in the user list. If i go to Server Admin I can see the users in the list here. > > Some mechanism in Pangolin is removing this user from the site. > > Disable Auto provisioning if you're not actively using it to assign roles/orgs. It fixes this issue. This sounds promising, I did turn this on after upgrading. Will disable and visit a try. Thanks!
Author
Owner

@joshdinsdale commented on GitHub (May 16, 2025):

I can confirm disabling auto provisioning worked for me.

@joshdinsdale commented on GitHub (May 16, 2025): I can confirm disabling auto provisioning worked for me.
Author
Owner

@jonzey231 commented on GitHub (May 16, 2025):

Awesome. Glad it's working now.

@jonzey231 commented on GitHub (May 16, 2025): Awesome. Glad it's working now.
Author
Owner

@Hutch79 commented on GitHub (May 19, 2025):

Same problem with Authentik.
Can confirm that disabling Auto Provisioning works as a Workaround.

@Hutch79 commented on GitHub (May 19, 2025): Same problem with Authentik. Can confirm that disabling Auto Provisioning works as a Workaround.
Author
Owner

@jonzey231 commented on GitHub (May 19, 2025):

Glad it's working now.

@jonzey231 commented on GitHub (May 19, 2025): Glad it's working now.
Author
Owner

@themadcodger commented on GitHub (May 21, 2025):

Ahh, this fixed it for me too.

@themadcodger commented on GitHub (May 21, 2025): Ahh, this fixed it for me too.
Author
Owner

@SiriXAU commented on GitHub (May 30, 2025):

I found the exact same issue, account was created & working in Pangolin with Pocket ID as the OIDC, everything worked, turned on auto provision to see what would happen and ran into this, seems like it's missing a way to make the connection with the organisation after this happens.

Ie. The auto-provision only seems to be able to provision a new user, and they need to create a new org? they can't select an existing one from their end, and the admin, although you can see the user in the Server Admin > All Users, you can't select the user and put them into an org seemingly.

@SiriXAU commented on GitHub (May 30, 2025): I found the exact same issue, account was created & working in Pangolin with Pocket ID as the OIDC, everything worked, turned on auto provision to see what would happen and ran into this, seems like it's missing a way to make the connection with the organisation after this happens. Ie. The auto-provision only seems to be able to provision a new user, and they need to create a new org? they can't select an existing one from their end, and the admin, although you can see the user in the Server Admin > All Users, you can't select the user and put them into an org seemingly.
Author
Owner

@kmanwar89 commented on GitHub (Jun 2, 2025):

+1 that disabling the auto provision worked.

@kmanwar89 commented on GitHub (Jun 2, 2025): +1 that disabling the auto provision worked.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 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.

@github-actions[bot] commented on GitHub (Jun 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.
Author
Owner

@sepffuzzball commented on GitHub (Jun 22, 2025):

Yeah I definitely had this issue - is there any way with the admin user to add either the admin or an OIDC user (I use Authentik) back into an Organization? Currently via the UI it seems I have no good way to add someone back to the org.

I've disabled auto-provision, but apparently since I created the org/site I was using as the OIDC user (I hate staying logged in as an admin) I can't seem to get to it.

Edit: Just looked up the schema and updated the database to insert my user so all good, but yeah, would be nice to fix!

@sepffuzzball commented on GitHub (Jun 22, 2025): Yeah I definitely had this issue - is there any way with the admin user to add either the admin or an OIDC user (I use Authentik) back into an Organization? Currently via the UI it seems I have no good way to add someone back to the org. I've disabled auto-provision, but apparently since I created the org/site I was using as the OIDC user (I hate staying logged in as an admin) I can't seem to get to it. Edit: Just looked up the schema and updated the database to insert my user so all good, but yeah, would be nice to fix!
Author
Owner

@myhrmans commented on GitHub (Jun 28, 2025):

Same issue here, as soon as they authenticate on a new device or after getting signed out they are removed from the organization.

@myhrmans commented on GitHub (Jun 28, 2025): Same issue here, as soon as they authenticate on a new device or after getting signed out they are removed from the organization.
Author
Owner

@miloschwartz commented on GitHub (Jun 30, 2025):

@myhrmans If auto provision is enabled, on each log in the policies you set are re-checked, so if the policies don't match the user to a org/role then they aren't put in that org (if they were previously in it, they'd be removed)

@miloschwartz commented on GitHub (Jun 30, 2025): @myhrmans If auto provision is enabled, on each log in the policies you set are re-checked, so if the policies don't match the user to a org/role then they aren't put in that org (if they were previously in it, they'd be removed)
Author
Owner

@boomam commented on GitHub (Jul 18, 2025):

Disabling auto-provision is not a solution, its a workaround.

This still needs to be investigated and resolved.

@boomam commented on GitHub (Jul 18, 2025): Disabling auto-provision is not a solution, its a workaround. This still needs to be investigated and resolved.
Author
Owner

@Hutch79 commented on GitHub (Aug 29, 2025):

Is there an update on this?
This bug limits the use of SSO severely and is still not fixed.

Is there a way as a non TypeScript savvy person to help fix this bug?

@Hutch79 commented on GitHub (Aug 29, 2025): Is there an update on this? This bug limits the use of SSO severely and is still not fixed. Is there a way as a non TypeScript savvy person to help fix this bug?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#348