[FR] Support OIDC.

[pinarruiz]

Adding OIDC support would allow for some existing user bases on different identity providers to use plane, specially on the self hosted plane, as many of us use Authentik, Keycloak or others to manage identities.

Having OIDC would also remove the need for Google and Github being mandatory.

[pablohashescobar]

Thank you for taking the time to submit this feature request. Please know that it’s already on our roadmap and we’re working hard to prioritize it. In the meantime, we encourage you to upvote this item to help us ensure it receives the attention it deserves.

[pinarruiz]

Hi, where can I see the roadmap, I know it was on the way, but I do not know where to find it.

[pablohashescobar]

Currently, we are using Plane to plan our roadmap. Since the GitHub Sync feature is now available, we will be moving our issues from Plane to GitHub

[PatrickHuetter]

+1 for keycloak. Solves all other auth issues since you could use id chaining.

[torbenraab]

Is there already a timeline for this one as it is listed on the website as a feature for a self-hosted instance?

[olivierlambert]

Login via OIDC (Keycloack in my case) is probably the only serious blocker to adopt it. Let us know if you need help to test it, I'll be happy to provide a test SSO account.

[torbenraab]

@olivierlambert Just checkout my PR and you can test it. I build everything according to the OpenID Spec. Testing was done with Authentik as we use it at our company

[olivierlambert]

Great! I will test it as soon I find how to build everything without Docker ^^

[RoshanCubastion]

Hey @pinarruiz ,
Can we implement Microsoft Entra ID OIDC to plane app ? What are all necessary nginx parameters required ?

[torbenraab]

@RoshanCubastion Please try the new PR. You just have to provide the issuer and client credentials from the Entra ID Provider. It should work as expected