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 must log in or # to comment.
I like Pocket ID. It’s also very simple to set up and just works™
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?).
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
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.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.
+1 for PocketID
@Lemmchen@feddit.org I just wanted to add a new service as I saw this page. May be helpful for you too: https://pocket-id.org/docs/client-examples
I use Authelia. I found it pretty easy to set up. They even provide guides with examples on how to integrate with other applications. For instance, I use Traefik for my reverse proxy: Traefik | Integration | Authelia
You can use a simple YAML file for your IdP or LDAP if you need more than a handful of users.
I just setup authentik in podman quadlet and got a lot of my services setup with it. Their documentation is actually very good and thorough. It covers a ton of services with easy to follow instructions.
Void auth, or kanidm look like easier alternatives.
Oidc is easier to implement than SAML. Oauth2 is for authorization (vs authentication). Its used along with Oidc, but Oidc is the authentication piece (the SSO part)
I say Oidc is easier to implement because it is json based (jwt token) vs SAML which uses XML, which is very verbose and has stuff like namespaces and xsd’s which can make XML a pain to work with.
I’d suggest you stick to keycloak and set up Oidc. This is a good tutorial https://medium.com/@buffetbenjamin/keycloak-essentials-openid-connect-c7fa87d3129d
Edit: take a look at authentik too. I’ve always used keycloak but authentik looks interesting
I’ve gone with Authentik for my homelab, and sure there is some learning to do, but it is fairly simple once it’s setup, and in the end it is not that bad.
If I were to choose over, I’d god with KeyCloak as it seems like that’s almost exclusively what’s used in the marked ~ and thus would be good to know in depth
.htaccessfiles are pretty simple to set up, if not hosting anything too sensitive.