Add new JWT profile that rename 'groups' claim with 'roles' #637
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
- Add access-token builder tests - Add scope-profile resolver tests - TO-DO: test userinfo/id-token/introspection responses
|
@jamesacris we opened this new PR and decided to rename profile from "keycloak" to "kc" because we want to avoid "copyright" problems :) You can checkout the new branch "issue-556-reloaded" if you want to contribute but the idea is that by the end of this morning we finalise tests and create a IAM docker image with these changes that can be tested. This docker image won't contain all the other stuff related to IAM v1.8.3 because it will be easier for you to upgrade your deployment with the official v1.8.3 when it will be released. |
and add tests
enricovianello
changed the title
|
Kudos, SonarCloud Quality Gate passed! |
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 'kc' profile wants to allow the integration with a Keycloak environment. Having "roles" claim instead of "groups" allows integration with the OIDC client - a conteinerised MISP deployment - which requires them to map IAM users.
This PR add this "kc" profile and: