Dealing with passkeys is kind of hassle for me. Does it get better after a while?
I’m asking because I started selfhosting PocketID and it ONLY has passkeys, no passwords and I have to decide if I keep it or not.
Dealing with passkeys is kind of hassle for me. Does it get better after a while?
I’m asking because I started selfhosting PocketID and it ONLY has passkeys, no passwords and I have to decide if I keep it or not.
I've installed Pocked ID recently and switched many of my self hosted services over to it, and I absolutely love it! It's pretty, it's fast, it works really well!
Pocket ID is an Open ID provider that you can use for self hosted Single Sign On.
I just wish more services supported it!
Gibt es irgendwas (ja, bis auf die Einschränkung, dass nur Passkeys funktionieren), was gegen #PocketID als Auth-Provider spricht?
(Ich habe im Homelab langsam zu viele Services und würde die gern auch etwas besser abgesichert wissen.)
I've been putting off some necessary maintenance and overall system streamlining on my home server for a while. Everything works, and services are secure and up to date, but I've got a bit of a messy setup that mixes #podman with #docker containers, #tailscale with #tsdproxy. I set this all up before I had my own domain, hence tsdproxy.
Now I have my own domain, I want to refactor my server using #netbird with #caddy and #pocketid.
It's a little daunting, but I'm going to take the plunge
As promised in the last weeknote, here's the write up for how I use #caddyserver and #pocketid to enable OIDC for my #calibre_web server
https://msfjarvis.dev/posts/setting-up-forward-auth-with-caddy-and-pocket-id/