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

Selfhosted

60093 readers
775 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
[–] fonix232@fedia.io 5 points 3 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.