Skip to content
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.

[Feature Request] Support OIDC or SAML Flows #220

Open
andrewkrug opened this issue Sep 4, 2019 · 2 comments
Open

[Feature Request] Support OIDC or SAML Flows #220

andrewkrug opened this issue Sep 4, 2019 · 2 comments

Comments

@andrewkrug
Copy link

It would be great to support standards compliant OIDC for integration as an alternative to the direct integration with the Okta API. This would open the door for Cerberus to integrate with a variety of auth providers (including Okta).

@fieldju
Copy link
Contributor

fieldju commented Sep 4, 2019

We have been talking about on turning Cerberus into a Gradle multi-project setup where different modules could be enabled / disabled via configuration. Very similar to how Kayenta is set up.

After we do this, we are thinking about scrapping the current user auth flow and creating a new one that is specific to OKTA (maybe it can be generic) and using the oath flow. This would establish a pattern for others wanting to make a module for XXXXX identity provider, and allow use to scrap our custom MFA stuff which doesn't work that well.

@andrewkrug
Copy link
Author

@fieldju I would of course advocate for a web standard. Okta and Auth0 both support great OIDC flows. I'd be happy to advise on how we've decoupled this in a couple of our other apps as well using an auth proxy.

@fieldju fieldju transferred this issue from Nike-Inc/cerberus Dec 11, 2019
@fieldju fieldju transferred this issue from Nike-Inc/cerberus-doc-site Dec 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants