Heiko
My feedback
11 results found
-
89 votes
An error occurred while saving the comment -
3 votesHeiko
supported this idea
·
-
23 votesHeiko
supported this idea
·
-
49 votesHeiko
supported this idea
·
-
63 votesHeiko
supported this idea
·
-
1,643 votesHeiko
supported this idea
·
-
1,311 votesHeiko
supported this idea
·
-
641 votesHeiko
supported this idea
·
-
29 votesHeiko
supported this idea
·
-
228 votesHeiko
supported this idea
·
-
597 votesHeiko
supported this idea
·
I run a homelab (Nextcloud, GitLab, and several other self-hosted services) and want my wife to use her own Proton account (we're both on the Family/Duo tier) to log into these
services via SSO, instead of maintaining separate local accounts for each app.
Most self-hosted apps I run already support "Login with OIDC" as an external provider (Nextcloud, GitLab, Authentik-fronted apps, etc.), so I don't need Proton to build anything app-specific. Just expose a standard OIDC discovery endpoint (/.well-known/openid-configuration) with the usual authorization_code flow, so any OIDC-compliant relying party can point at Proton.
This shouldn't be limited to Business/Enterprise. For home users on Unlimited/Family/Duo plans this would remove the need to run a separate identity provider (like Keycloak or Authentik) just to unify logins for family members, which is a real barrier for people trying to get non-technical family onto self-hosted alternatives instead of Google/Microsoft.