fix(keycloak): handle situations where the systemInfo.version isn't available#8406
Open
PatAKnight wants to merge 2 commits intobackstage:mainfrom
Open
fix(keycloak): handle situations where the systemInfo.version isn't available#8406PatAKnight wants to merge 2 commits intobackstage:mainfrom
PatAKnight wants to merge 2 commits intobackstage:mainfrom
Conversation
…vailable Signed-off-by: Patrick Knight <pknight@redhat.com>
Signed-off-by: Patrick Knight <pknight@redhat.com>
Contributor
Changed Packages
|
|
Running into this, so thanks for fixing! :) |
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
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.
Hey, I just made a Pull Request!
Handles cases where
systemInfo.versionis unavailable in the Keycloak server info response. Starting with Keycloakv26.4.0,systemInfois only accessible from the master realm — retrieving it from any other realm requires granting additional roles to that realm'srealm-managementclient. Rather than making this an extra configuration requirement for users, the plugin now defaults toprocessGroupsRecursivelywhen the server version cannot be determined, only falling back to the legacytraverseGroupspath when a version is explicitly detected as 22 or lower.Fixes
✔️ Checklist
Signed-off-byline in the message. (more info)