fix(authz-keycloak): strip query string when resolving resources with lazy_load_paths #12914
+82
−1
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
Summary
ctx.var.uriinstead ofctx.var.request_uriwhen resolving resources withlazy_load_paths=true, ensuring query parameters are stripped before sending to Keycloak's resource registration endpointWhat's the problem?
When
lazy_load_paths=trueis enabled, the plugin incorrectly includes query parameters when calling Keycloak's UMA resource registration endpoint (resource_set?matchingUri=true). This causes Keycloak to fail resource matching with "invalid_resource" errors.For example, a request to
/api/items?country=eswould send the full URI including query string to Keycloak, which cannot match it against a resource configured with URI/api/items.What's the solution?
Replace
ctx.var.request_uri(path + query string) withctx.var.uri(path only) when resolving resources. This aligns with Keycloak's official Policy Enforcer behavior which usesrequest.getRelativePath().Which issue(s) this PR fixes:
Fixes #12785
Checklist