Open Simon-Boyer opened 8 months ago
MAHDTech
commented
7 months ago Having recently spent time migrating a bunch of our SAML k8s apps over to OpenID connect I could really use this to help pitch the omni case in my org
We're using pinniped.dev
samip5
commented
5 months ago Add OIDC as a third option to omni auth providers methods (currently only auth0 and saml).
OIDC as in OpenID Connect?
Simon-Boyer
commented
5 months ago Add OIDC as a third option to omni auth providers methods (currently only auth0 and saml).
OIDC as in OpenID Connect?
Yes
bauerjs1
commented
3 months ago Is there any progress here? It looks like #126 addressed this problem but I cannot find any documentation on how to use it, yet.
Generic OIDC support would really be a huge benefit since it would allow us to use, e.g., Dex as an adapter to pretty much any corporate ID Provider (Dex might also serve as a good OIDC example in the docs with its "Mock" provider).
I tried to use Auth0/OIDC auth with Keycloak but Omni always appends /authorize to the auth endpoint which does not match the correct path in Keycloak. I assume it does not look up the .well-known/openid-configuration OIDC endpoint, where all endpoints are discoverable.
stereobutter
commented
3 months ago +1 for Dex support as that would enable some other identity providers and more complex setups via adapters.
bauerjs1
commented
2 weeks ago Any updates on this? Am I missing some configuration?
Problem Description
I'm trying to use an identity provider which currently only supports OIDC, it would be nice if it was one of the supported options for omni.
Solution
Add OIDC as a third option to omni auth providers methods (currently only auth0 and saml).
Alternative Solutions
Tried to use this thing, but I cant make it work: https://github.com/IdentityPython/SATOSA/tree/master
Notes
No response