Quick Connect for Jellyfin

Feature description:

As saying in previous posts, it would be great to use SSO for jellyfin login. Currently, in my self hosted apps, jellyfin is the only one require a password + login in order to let Symfonium connect. Jellyfin has an SSO plugin which is working well. I have two main questions :

  • Is there a way, like for Plex, to use the jellyfin login web page instead of just login + credentials in order to establish a session
  • If not, is it possible to use the Quick Connect jellyfin code instead ? Thanks to that, users would connect on web browser and compatible apps via SSO, and quick connect for Symfonium client

Thanks :slight_smile:

Problem solved:

There is only one way to login to Jellyfin currently

Brought benefits:

It improves jellyfin security by not letting people connect with credentials

Other application solutions:

 
Jellyfin app is based on the web app I think, so the SSO integration works well. There is no Jellyfin clients that support SSO currently
 

Additional description and context:

 

 

Screenshots / Mockup:

    

2 Likes

Had to make an account just to bump this. I would love to see this implemented in some way.

Currently I am using LDAP as my backend for my Jellyfin users, meaning if they have 2FA enabled they can log in with a semi colon i.e. “password;123456”

However Symfonium is currently handling the jellyfin login horribly breaks this. I think it’s constantly pinging and updating the user password and instantly invalidating that 2FA code. This isn’t a problem for other apps like Jellyseerr or Feishin.

So cannot use 2FA and symfonium.

Unrelated, open a proper issue.

It’s not unrelated and I’m not opening a new issue because I’m not specifically asking for a fix, maybe another day.

Bumped this thread because using quick connect specifically is something I’d like to see, it solving my LDAP issue is a bonus.

Well I am actually asking for a fix :wink:

There’s nothing more infuriating to be given half the details of a bug and having no way to fix it :wink:

So can you pretty please open the issue ?