Desktop Client with Authentik OAuth

[dnightbane]

Hello!

I recently installed Jellyfin, and have connected it with Authentik for SSO. This works great for the browser however when I try to login with SSO on the desktop client I just get a black screen after hitting "Sign in with SSO" (shown below). Is there something I'm missing in the setup or is LDAP the only option (This would require setting a local password on the OAUTH user so not necessarily the ideal scenario)?

Initial screen when opening the app
   

After hitting the Sign in with SSO button
   

[TheDreadPirate]

Which server version are you running and what version of Jellyfin Media Player? Also, are you using a reverse proxy?

[dnightbane]

Apologies, that would be useful information to include.

Jellyfin Version: 10.10.6 (docker)
Jellyfin Player Version: 1.11.1 (Windows)
Reverse Proxy: Nginx (docker)

[TheDreadPirate]

Can you go over this walkthrough another forum user wrote?

https://forum.jellyfin.org/t-jellyfin-au...n-tutorial

Double check your setup lines up with their walkthrough?

And can you provide your Nginx config? Censor the domain.

[dnightbane]

Definitely a good guide for LDAP with 2FA, thank you!

That post also made me realize my initial post was missing a few more details, apologies about that.

The authentik flow for this domain is set to OAUTH with plex.tv (Figured this would be an easy way to allow my users to choose whichever they want without having to maintain multiple credentials) so when a user goes to https://jellyfin.domain.com they are instantly redirected to authentik which pops a login for plex.tv. This works as expected in the browser but I suspect may not be a supported configuration for the clients so LDAP and different credentials may be the route I need to go.

My nginx config
server {
listen 443 ssl;
http2 on;
server_name jellyfin.domain.com;
include /etc/nginx/conf.d/https.conf;

## The default client_max_body_size is 1M, this might not be enough for some posters, etc.
client_max_body_size 20M;

# Security / XSS Mitigation Headers
add_header X-Content-Type-Options "nosniff";

# Permissions policy. May cause issues with some clients
# add_header Permissions-Policy "accelerometer=(), ambient-light-sensor=(), battery=(), bluetooth=(), camera=(), clipboard-read=(), display-capture=(), document-domain=(), encrypted-media=(), gamepad=(), geolocation=(), gyroscope=(), hid=(), idle-detection=(), interest-cohort=(), keyboard-map=(), local-fonts=(), magnetometer=(), microphone=(), payment=(), publickey-credentials-get=(), serial=(), sync-xhr=(), usb=(), xr-spatial-tracking=()" always;

# Content Security Policy
# See: https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
# Enforces https content and restricts JS/CSS to origin
# External Javascript (such as cast_sender.js for Chromecast) must be whitelisted.
add_header Content-Security-Policy "default-src https: data: blob: ; img-src 'self' https://* ; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://www.gstatic.com https://www.youtube.com blob:; worker-src 'self' blob:; connect-src 'self'; object-src 'none'; frame-ancestors 'self'; font-src 'self'";

access_log /var/log/nginx/jellyfindomain/jellyfin.access.log;
error_log /var/log/nginx/jellyfindomain/jellyfin.error.log;

location / {
# Proxy main Jellyfin traffic
proxy_pass http://jellyfin:8096;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Protocol $scheme;
proxy_set_header X-Forwarded-Host $http_host;

# Disable buffering when the nginx proxy gets very resource heavy upon streaming
proxy_buffering off;
}

location /socket {
# Proxy Jellyfin Websockets traffic
proxy_pass http://jellyfin:8096;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Protocol $scheme;
proxy_set_header X-Forwarded-Host $http_host;
}
}

[TheDreadPirate]

The Nginx config looks fine. But I don't think your current flow will work with a lot of clients so, as you said, you will probably need to go the LDAP route.

[Duvel]

The clients capabilities are really the bottleneck in using OAUTH/SSO pluggin. IMO Its not usable in the actual state because of this and should be disregarded.

Everyone that use or have users using different clients than web (which is most probably the case of everyone), can only use the LDAP pluggin if they want proper working SSO.... And LDAP is much, MUCH harder to setup.

It would be nice if the Jellyfin team could emphasis on the importance to implement SSO OAUTH correctly in the clients. We are in 2025... I just dont get how client devs still dont realize that its not a "nice-to-have" anymore. Its rather a must-have to not say an obligation.