fix: correct Bearer token formatting in UMA rego policy for Keycloak#904
Merged
silvi-t merged 1 commit intoKuadrant:mainfrom Mar 25, 2026
Merged
fix: correct Bearer token formatting in UMA rego policy for Keycloak#904silvi-t merged 1 commit intoKuadrant:mainfrom
silvi-t merged 1 commit intoKuadrant:mainfrom
Conversation
…26.5.4+ Signed-off-by: Silvia Tarabova <starabov@redhat.com>
azgabur
approved these changes
Mar 25, 2026
averevki
approved these changes
Mar 25, 2026
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.
Summary
Details
Keycloak 26.5.4 includes a fix for CVE-2026-0707 ("Incorrect Behavior Order: Authorization Before Parsing and Canonicalization"), which enforces stricter
Authorizationheader parsing per RFC 6750.The OPA rego policy in
test_authorization_services.pywas constructing malformed Authorization headers usingconcat(" ", ["Bearer ", token]). Since OPA'sconcatjoins array elements with the separator, and"Bearer "already has a trailing space, this produced"Bearer <token>"(double space).The old Keycloak parser was lenient and accepted this; the new parser rejects it.
Verification steps