New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught server error: java.lang.IllegalArgumentException: Path parameter not provided #27514
Comments
Hi, when you build the URL to return in the response location here, |
Due to the amount of issues reported by the community we are not able to prioritise resolving this issue at the moment. If you are affected by this issue, upvote it by adding a 👍 to the description. We would also welcome a contribution to fix the issue. |
The role is encoded to avoid template resolution by the URIBuilder. This fix avoids the exception when creating roles with names containing {patterns}. Closes keycloak#27514 Signed-off-by: graziang <g.graziano94@gmail.com>
The role is encoded to avoid template resolution by the URIBuilder. This fix avoids the exception when creating roles with names containing {patterns}. Closes keycloak#27514 Signed-off-by: graziang <g.graziano94@gmail.com>
The role is encoded to avoid template resolution by the URIBuilder. This fix avoids the exception when creating roles with names containing {patterns}. Closes #27514 Signed-off-by: graziang <g.graziano94@gmail.com>
The role is encoded to avoid template resolution by the URIBuilder. This fix avoids the exception when creating roles with names containing {patterns}. Closes keycloak#27514 Signed-off-by: graziang <g.graziano94@gmail.com>
@mposolda this sounds like something that would justify a backport to 24, no? |
Thanks @graziang! |
The role is encoded to avoid template resolution by the URIBuilder. This fix avoids the exception when creating roles with names containing {patterns}. Closes keycloak#27514 Signed-off-by: graziang <g.graziano94@gmail.com> (cherry picked from commit 39299ee)
Before reporting an issue
Area
oidc
Describe the bug
I'm trying to create a Client Role in Keycloak for using a RabbitMQ Topic exchange. RabbitMQ allows for variable expansion based on token claims, using roles like
rabbitmq.write:*/q-{vhost}-*/u-{sub}-*
When i try to create this Client Role though, keycloak appears to substitute the
{sub}
, for which it has no value, resulting in a HTTP 500.I can find no documentation on the substitution behaviour. Is there a way i can disable this substitution?
Version
24.0
Regression
Expected behavior
The Client Role gets created.
Actual behavior
No role gets created, the server returns a HTTP 500 and outputs:
How to Reproduce?
{pattern}
in the nameAnything else?
No response
The text was updated successfully, but these errors were encountered: