-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSO login not working after changing username #146
Comments
If you set the preferred claim to "sub", it'll work automatically. It will make the usernames in Jellyfin ugly, though. |
Perhaps linking can be expanded so that it maps |
That does not solve it for me. Still unlinks once the Jellyfin username gets changed by an admin. I thought that this was possible:
Is the SSO user mapped to the Jellyfin username or to the Jellyfin UID? |
When linking, the SSO username claim is mapped to Jellyfin's user UID. |
Ideally, we can switch to using |
After looking into the code, it seems this line is the culprit:
As I understand it, it only works when the |
Yes, that is on the roadmap. It isn't implemented quite yet. |
I have accidentally renamed my user account, and then a new user with the old name was created by this plugin. I removed that user. Now my sso is no longer working.
How can I make it working again? |
Stop Jellyfin, and edit the |
Describe the bug
I have an existing Jellyfin user account and an Authentik account. Jellyfin SSO plugin is setup for OpenID. The usernames are different. Two (probably related) issues:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Be logged in as the already linked user.
Screenshots
Not needed.
Configuration
Not needed.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: