this post was submitted on 24 Mar 2026
58 points (96.8% liked)

Selfhosted

59864 readers
165 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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
[–] MrPnut@lemmy.world 2 points 2 months ago* (last edited 2 months ago)

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