#openidconnect

@dansup@mastodon.social Thanks — that is good news, especially for Loops. Unless I am missing something, though, Pixelfed's OIDC support is not yet operator-friendly: I could not find a documented, supported .env configuration for issuer URL, client ID, client secret, scopes and redirect URI. So far I have had to modify configuration inside the container, which makes upgrades and reproducible Docker deployments unnecessarily painful. A first-class .env interface — ideally documented and usable through Docker Compose secrets — would make Pixelfed's OIDC support actually practical for self-hosted instances. Is that planned as well? #OpenIDConnect #Pixelfed #SelfHosting

@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