Submitted 7 hours ago by Lemmchen@feddit.org to selfhosted@lemmy.world
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?
Protocol-wise, OIDC is generally the most supported out there. LDAP too, to an extent.
Software wise, I find Kanidm quite simple to set up (basically just one container). It’s mostly managed via the terminal though, and lacks some eyecandy. But some of the examples in its docs should be easy to follow and get you familiar with mapping scopes/groups between Kanidm and services.
Authelia is okay too
I honestly didn’t find authentik very complicated. You can be up and running pretty much after starting it. I used docker to run it.
What’s the difficulty with keycloak? I just set this up last weekend
https://oneuptime.com/blog/post/2026-03-18-run-keycloak-podman-container/view
I think this might be on of those cases where the TUI is actually easier to understand than the WebUI. In the WebUI there are tons of terms I’ve never even heard before, but this actually looks kinda straight forward. Thanks!
Oh absolutely! I try to always start from cli and config files first personally so keycloak made a lot of sense to me. Good luck with whatever you choose.
I quite lldap too. I wish there was an easy way to glop oauth ontop of it.
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
.htaccess files are pretty simple to set up, if not hosting anything too sensitive.
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 medium.com/…/keycloak-essentials-openid-connect-c…
Chaser@lemmy.zip 7 hours ago
I like Pocket ID. It’s also very simple to set up and just works™
pocket-id.org
HybridSarcasm@lemmy.world 7 hours ago
+1 for PocketID
Lemmchen@feddit.org 7 hours ago
I’d live 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 (has anybodz experience with that?).
Chaser@lemmy.zip 7 hours ago
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