Replies: 1 comment 1 reply
-
|
so would that mean that the new local user created in jellyfin has no password? I would do 1 of 2 things:
See how, if at all, it affects your keycloak SSO scenario. The current setup is more geared towards the regular users, your setup is a bit more customized. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I don't know how to wrap my head around this, I can't seem to figure it out.
I got Jellyfin and Seerr to log in using Google SSO through KeyCloak + SSO-Auth. Here's the flow:
All of this works well for now and nobody has to remember passwords. Very cool, I just got this working last week and I like this.
I want even easier and prettier for my folks, so I decided Moonfin would be ideal. The main draw was Seerr integration into the UI. I read in the github "Moonfin now uses a proxy-first Seerr integration: iframe and API traffic are routed through Jellyfin for seamless SSO" and I misunderstood the SSO part, thinking I'd be able to employ SSO with Moonfin also.
I'm not a dev so help me understand, Jellyfin local accounts are for Library permissions, the SSO-Auth + KeyCloak accounts are for authentication, and Jellyfin local accounts that are tied to an SSO login don't have passwords, correct?
In my schema, how can true SSO logins utilize Seerr integration through Moonfin? If it's not possible yet, how could it be implemented?
Beta Was this translation helpful? Give feedback.
All reactions