58
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Mar 2026
58 points (100.0% liked)
Selfhosted
60623 readers
496 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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
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
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.
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.
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.
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.