Comment

Are you doing auth in the reverse proxy for Jellyfin? Do you use Chromecast or any non-web interface? If so I’m very interested how you got it to work.

source

Sort:hotnew top

Shimitar@feddit.it ⁨2⁩ ⁨months⁩ ago
This is my jellyfin nginx setup: wiki.gardiol.org/doku.php?id=services:jellyfin#re…

currently i don’t use any proxy related authentication because i need to find the time to work with the plugins in Jellyfin. I don’t have any chromecast, but i do regularly use the Android Jellyfin app just fine.

I expect, using the OIDC plugin in jellyfin, that Jellyfin will still manage the login via Authelia itself, so i do not expect much changes in NGINX config (except, maybe, adding the endpoints).

source
- kevincox@lemmy.ml ⁨2⁩ ⁨months⁩ ago
  Ah ok. You aren’t doing auth. So sort of irrelevant to the whole discussion.
  
  source
  - Shimitar@feddit.it ⁨2⁩ ⁨months⁩ ago
    Well, here is the relevant part then, sorry if it was not clear:
    
    Jellyfin will not play well with reverse proxy auth. While the web interface can be put behind it, the API endpoints will need to be excluded from the authentication (IIRC there are some examples on the web) but the web part will stil force you to double login and canot identify the proxy auth passed down to it.
    
    Jellyfin do support OIDC providers such Authelia and it’s perfectly possible to link the two, in this case as i was pointing out, Jellyfin will still use it’s own authentication login window and user management, so the proxy does not need to be modified.
    
    TLDR: proxy auth doesnt work with Jellyfin, OIDC yes and it bypassess proxy, so in both cases proxy will not be involved.
    
    source