FEAT: Update Keycloak config for client roles rather than realm roles #43
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
…ludes new methods to check roles from a given client. CHORE: Update config for latest version and clean up some configurations.
Gonzo345
approved these changes
Mar 7, 2023
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.
Description
Closes #42 and implements new methods for checking roles belonging to a client.
Also performs some cleanup of configurations and upgrade to latest version of Keycloak.
Related Issue
Closes #42.
Motivation and Context
Allows better and more flexible management of roles for different resources (APIs) and allows to check for them beyond the standard
roleclaim in the tokens.Types of changes
Checklist: