feat(keystone): add OAuth 2.0 authentication options #1496
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The device authorization and the client credentials flows are OAuth 2.0 flows instead of OIDC so we need to be able to validate the token submitted against the endpoint so we need to also read the metadata for the OAuth 2.0 paths of mod_auth_openidc. Add another authentication endpoint into apache for Keystone so that we can route the authentication request to the correct connector inside of Dex to successfully complete the authentication.
Add additional env vars to be loaded to make the naming clearer that these are for connectors and not for regular client authentication.
skrobul
approved these changes
Dec 11, 2025
| <Location /v3/OS-FEDERATION/identity_providers/sso/protocols/mapped/auth> | ||
| Require valid-user | ||
| AuthType oauth20 | ||
| # TODO: variablize this better |
Collaborator
There was a problem hiding this comment.
looks like the helm templating is supported here, so maybe just make it a configurable value with a sensible default?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The device authorization and the client credentials flows are OAuth 2.0 flows instead of OIDC so we need to be able to validate the token submitted against the endpoint so we need to also read the metadata for the OAuth 2.0 paths of mod_auth_openidc. Add another authentication endpoint into apache for Keystone so that we can route the authentication request to the correct connector inside of Dex to successfully complete the authentication.