Assuming the user will not be connecting over vpn, but is both remote and non-technical, how would you expose Jellyfin to them securely?

you are viewing a single comment's thread
view the rest of the comments
[–] 13 points 5 months ago (7 children)

The biggest problem with that Jellyfin to this day is that you can’t.

Seems like every new open source selfhosted app implements OIDC compatibility, but for some reason, I can only assume is technical debt, Jellyfin hasn’t.

  • source
  • hideshow 7 child comments
  • [–] 2 points 5 months ago (3 children)

    Jellyfin had a third party plugin for OIDC. It was archived recently, but I heard Jellyfin has plans to implement it directly into the software. 🤞

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 5 months ago (2 children)

    The plugin was neat, but if the clients don’t support it, it’s pretty much useless.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 5 months ago (1 child)

    Mobile clients should use QuickConnect for it (statement by the sso plugin maintainer). Else it should work with everything that uses the WebUI.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 5 months ago*

    Quick connect is not SSO. Because the topic is about non-technical end user friendly solutions, this isn’t a great one because this requires your user to login using a web browser on a different device and then use that for the quick connect and it’s just more clunky than it should really be.

    It’s honestly easier in this situation to just configure your end users device with a mesh VPN like Tailscale or Netbird and then all they ever have to do is login with whatever password you gave them.

  • source
  • parent
  • [–] [S] 1 point 5 months ago (2 children)

    What exactly about jellyfin makes this oidc style access more difficult to manage?

  • source
  • parent
  • hideshow 2 child comments