#openid

3 posts · Last used 13h

📢 Account move notification Almost everything is ready to move my social home to @fabio@manganiello.tech (@fabio@manganiello.tech). The new account runs on #Yonder. Yonder is a social platform I’ve been working on for a while, and I’ll soon write about it more in detail. It’s an #ActivityPub server written in #Rust and fully compatible with Mastodon and Pleroma/Akkoma, plus with other #Indieweb features I like (support for #Webmentions, and #OpenID coming soon). Plus it implements features (like on-demand remote fetch of statuses/threads context, support for Threadiverse-like actors, OAuth-based account migration that also includes posts and interactions without needing to move CSV files around, better storage management…) that I’ve wanted in those platforms for a while but I’ve struggled to get merged. If you follow me here, you can hit the follow button on the new account (and if you don’t, don’t worry, my followers will be migrated at some point between today and tomorrow).
0
1
1
0
Replying to
@dansup@mastodon.social Full agree: the Fediverse needs to become easier and more familiar to use. But that should mean open, self-hostable standards too. I would really like to see #OIDC / #OpenID Connect as a built-in option — like #Mastodon supports, or #PeerTube can gain through plugins — alongside Sign in with Apple, Google, etc. For Pixelfed, an easy .env-based configuration for a generic OIDC provider would be ideal: issuer URL, client ID, client secret, scopes, redirect URI — done. That would let instance admins use #Keycloak, #Authentik, #Zitadel, their university/work SSO, or any other compatible provider. Does #Loops have plans for generic OIDC login? And is this planned for #Pixelfed as well? Making sign-up familiar matters. Making it interoperable and self-hostable matters just as much. #OpenIDConnect #SelfHosting #Fediverse
6
4
2
0

Achievement unlocked: SSO for the hypervisor! 🎉

My Proxmox VE is now officially using Keycloak OIDC for authentication, and the setup is fantastic:

  • Centralized Users: Managed alongside my other apps (Keycloak using my LDAP as the backend).

  • Hardware MFA: Locked down with a FIDO2 stick from @nitrokey@social.nitrokey.com

  • Unified Control: Centralized policies, logging, and RBAC across the board.

Another great improvement for my HomeLab/SelfHosting setup.

#Proxmox #Keycloak #DevOps #Auth #OpenID #Homelab #SelfHosted

22
3
11
0