@RolesAllowed doesn't respect comma escapes in property values
#37390
Labels
Comments
|
You added a link to a Zulip discussion, please make sure the description of the issue is comprehensive and doesn't require accessing Zulip This message is automatically generated by a bot. |
coiouhkc
pushed a commit
to coiouhkc/quarkus
that referenced
this issue
Nov 29, 2023
…sing double-escape
|
/cc @pedroigor (bearer-token), @sberyozkin (bearer-token,jwt,security) |
coiouhkc
pushed a commit
to coiouhkc/quarkus
that referenced
this issue
Nov 30, 2023
…sing double-escape
coiouhkc
pushed a commit
to coiouhkc/quarkus
that referenced
this issue
Nov 30, 2023
…sing double-escape
|
Fixed by #37436 |
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Dec 1, 2023
…sing double-escape (cherry picked from commit b045e66)
holly-cummins
pushed a commit
to holly-cummins/quarkus
that referenced
this issue
Feb 8, 2024
…sing double-escape
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using
@RolesAllowed("${admin}")syntax, cannot use LDAP groups as roles, since comma escaping in property value (to prevent parsing it as list instead of single entry).Also related (initial implementation?): #33982
See https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/.E2.9C.94.20RolesAllowed.20annotation.20value.20containing.20comma
Expected behavior
Escape syntax of smallrye-config is respected
Actual behavior
Escape syntax of smallrye-config is respected
How to Reproduce?
See linked PR for additional test.
Output of
uname -aorverNo response
Output of
java -versionNo response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: