OIDC Strict cannot handle existing users if OIDC connection is mismatched · Issue #2225 · tgstation/tgstation-server · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
8000
Describe the bug
As explained on discord, OIDC strict mode prevents all user editing, and aborts logins if it ever tries to create a user that already exists.
To Reproduce
Steps to reproduce the behavior:
Start TGS in non-strict OIDC
Create a user with a CanonicalName that will be a future OIDC connection (but either have no OIDC connection or have something that isn't the new OIDC connection exactly)
Restart TGS in strict OIDC
Attempt to log in as the previously created user
Expected behavior
User is able to log in (existing entry is trampled/edited)
Also of note, it seems it will write a new entry to db when attempting to create a new user, and this will also break all future attempts for that user to log in because they don't have an OIDC connection set, and the username can collide.
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
As explained on discord, OIDC strict mode prevents all user editing, and aborts logins if it ever tries to create a user that already exists.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User is able to log in (existing entry is trampled/edited)
Logs
error.txt
Server State: (please complete the following information):
Additional context
https://discord.com/channels/484170914754330625/653425022966169620/1373802880577966182
Solutions:
update OidcConnections set ExternalUserId='NEWOIDC' where ExternalUserId='OLDOIDC';
The text was updated successfully, but these errors were encountered: