Document binding existing accounts when setting up SSO after creating local accounts #18
Reference in New Issue
Block a user
No description provided.
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?
Magic hack: https://community.hedgedoc.org/t/how-to-bind-an-oauth2-user-to-an-ldap-user/1128/2
Actually it does already work but users lose all their history! Here's how to avoid that....
You might need to create a dummy test user first using your SSO login.
DONT use an email which clashes with an existing user. It will bind and delete all their history.
Then you'll be able to select that user in the db and see the
profile
/profileid
entry.For me (using
rauthy
), it was (with dummy values):This
bazbaz
is the ID value that is sent from my SSO provider. Check your SSO admin user management view.Then, you update the user you want to bind and not lose history with those two fields.
Then log in with your SSO and you should still have your history + it binds.