-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
EL Placeholder support in @RolesAllowed annotation #25245
Comments
Hi @radcortez, @dmlloyd Is it something that our configuration system can help with ? I guess it should work similar to this:
I believe such a resolver code already exists since we already support such indirect property references in Thanks |
Sure, it should be possible. The expression resolution is performed by |
hi @sberyozkin agreed. and that has been supported for many years in jboss. |
hello, do you think this is likely to be implemented at some point? |
Ideally if this could come from the community it would be faster :) |
thanks for this honest answer @radcortez ;) |
Great. Thanks. Feel free to reach out if you need help. |
Looks like interesting issue, I can have a look provided @vsevel is fine with that. |
sure. np. happy to test if you need. @michalvavrik |
Thank you. |
Describe the bug
If we use an EL placeholder in @RolesAllowed annotation value, to make a reference to a config property, the placeholder is not resolved.
Example:
MyClass.java
application.yml
This is something that works with Jakarta EE on EAP/Wildfly so I expected it to work also with Quarkus.
Expected behavior
@RolesAllowed annotation value resolved to "myrole_someValue"
Actual behavior
@RolesAllowed annotation value remains "myrole_${role.suffix}"
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: