58
Easiest to set up IAM solution? (OIDC, OAuth2, SSO, etc.) (feddit.org)
submitted 4 months ago by to c/selfhosted@lemmy.world
28 comments fedilink hide all child comments
 

I've just looked at some tutorials for Keycloak and Authentik and there's definitely a very steep learning curve for these two solutions. I feel like I need something a lot simpler to be able to fully grasp the concept.

What is the easiest solution for beginners to implement Sigle-Sign-On for their selfhosted services?

you are viewing a single comment's thread
view the rest of the comments
[–] 20 points 4 months ago (3 children)

I like Pocket ID. It's also very simple to set up and just works™

https://pocket-id.org/

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] [S] 4 points 4 months ago* (1 child)

    I'd love to use PocketID, but I fear my users aren't really set up to use passkeys (they're awesome!) and I assume they wouldn't work on the Android TV Jellyfin client (does anybody have experience with that?).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 4 months ago (3 children)

    That may be a problem, because Pocket ID works with Passkeys only. But you can also configure Emails, so your users can get one time login links.

    Regarding Jellyfin: You can login on your phone using oidc. On the TV you can use Quick Connect then

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 5 points 4 months ago

    Technically true, BUT.

    PocketID does offer a fallback to a numeric code for clients that don't support passkeys (e.g. most embedded webviews on mobile).

    For those, you simply need to navigate to the PocketID interface (for less technically adept people you can put it on the home screen on their phones), and click the big center button "Create" in the "Login Code" section (see attached screenshot).

    Unfortunately these login codes are long lived (10-15 minute I believe?) and aren't OTP compatible so you can't just register it in a code provider to use whenever needed.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 3 points 4 months ago* (last edited 4 months ago) (1 child)

    If they can use their phones to log in with passkeys this might just work, hmm. I'll definitely take a closer look at that then. Thank you!

    Edit:
    That's very unfortunate as my users will basically only use the Android or Android TV app and not a browser. Maybe it's not too bad if it is a one time thing, but it definitely makes it not ideal.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 4 months ago

    Jellyfin is actually the only self hosted service I don't use LDAP or OIDC on purpose. Jellyfin is used only by me, my wife and sometimes a guest. So I just created the accounts by hand. I did so, because I want empty passwords there, so we can easily login. On the android tv app the login screen behaves like the Netflix profile selection screen, if the passwords are empty.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 4 months ago (1 child)

    Also, Jellyfin supports LDAP backing, so OP could set up PocketID with an LLDAP backing server (minor extra complexity). Managing passwords will still be a chore as PocketID does not support neither setting them up nor syncing it with LDAP (it can read and authenticate LDAP users, not write them), but then Jellyfin can work without the OIDC plugin, just using the LDAP login approach.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 4 months ago

    Yeah, I've just realized that Jellyfin doesn't have native OIDC support and requires a third-party plugin for that functionality. Maybe going all-in instead on a LDAP solution is the right way then? But I think most common selfhostable software only supports OIDC and not necessarily LDAP. I might be wrong though.

  • permalink
  • fedilink
  • source
  • parent