This repository was archived by the owner on Nov 26, 2025. It is now read-only.
feat: add roleAttributePath parameter to OIDC configuration #134
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
Add configurable roleAttributePath field to allow extraction of user roles from custom locations within OIDC token claims. This enables support for different OIDC providers that may structure role information differently in their JWT tokens. - Add roleAttributePath field with documentation - Default value set to "roles" for backward compatibility - Includes example usage for nested token structures
Contributor
|
Hi @mayrf, Could you please also add information about the OIDC roles to the README? You can find it here: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Add configurable roleAttributePath field to allow extraction of user roles from custom locations within OIDC token claims. This enables support for different OIDC providers that may structure role information differently in their JWT tokens.