Support keycloak custom format via configuration #13216
Draft
+291
−118
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
Update existing test case with the appropriate configuration Add more tests
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.
Proposed Changes
Implements feature #12324
Notes that should be included into the release notes:
Any RabbitMQ cluster which receives JWT tokens from Keycloak using the structure authorization.permissions.scopes (for more information, check #12324) should add the following line to their configuration. From this release onwards, RabbitMQ will not extract scopes from that location unless you explicitly configure it.
Docs pr:
Types of Changes
What types of changes does your code introduce to this project?
Put an
xin the boxes that apply