Add configuration to extract the user id from an OpenID Connect non-standard claim #31
Conversation
This file contains 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
…tandard claim New config property `georchestra.gateway.security.oidc.claims.id.path` allows to use an OIDC non-standard claim to extract the user identifier. The gateway config must set the `georchestra.gateway.default-headers.userid: true` property to send the `sec-userid` request header to all services.
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.
New config property
georchestra.gateway.security.oidc.claims.id.pathallows to use an OIDC non-standard claim to extract the user identifier.The gateway config must set the
georchestra.gateway.default-headers.userid: trueproperty to send thesec-useridrequest header to all services.