Post #4495753
2026-08-11 00:15 UTC
I'm considering self-hosting Pocket ID to use as an OIDC identity provider for various other self-hosted services. It's small and simple and easy to understand, but there's a big gap: high availability. If I set up an instance on a machine somewhere, and that machine dies, every service using it as an IdP is temporarily inaccessible until the situation is cured.
How do other self-hosters address this situation? I understand at some point there are single points of failure, but I'd like to avoid this being one.
#SelfHosting #OIDC #Homelab
Replies (3)
-
@gary_alderson@infosec.exchange 2026-08-11 00:33
@kevin@mastodon.km6g.us use proxmox HA and round robin dns? rsync, keepalived, i think if you use a shared db failover should work pretty quickly minimize downtime
-
@a@852360996.91268476.xyz 2026-08-11 01:54
@kevin@mastodon.km6g.us the question is why would it fail? It certainly can, but I guess you can run multiple replicas una kubernetes cluster (a bit overkill IMO)
-
@kevin@mastodon.km6g.us 2026-08-11 12:59
Update: I received multiple suggestions to use Kanidm instead, since it is also lightweight but has built-in support for replication. I'll go that route!