You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please help me to understand if this is expected behaviour or a bug.
When I configure quarkus.http.auth.permission.* and quarkus.http.auth.proactive=false in a reactive-routes application, Quarkus is not resolving resource methods returning non mutiny types.
e.g.
with below config
quarkus.http.auth.proactive=false
# PermitAll policy for metrics endpoint. Same as @PermitAll annotation
quarkus.http.auth.permission.permit.paths=/q/*
quarkus.http.auth.permission.permit.policy=permit
# Authenticated policy for groups and logout endpoints. Same as @Authenticated or @RolesAllowed("**") annotation
quarkus.http.auth.permission.loggedin.paths=/api/*
quarkus.http.auth.permission.loggedin.policy=authenticated
following resources are not resolved and clients will eventually timeout.
Issue is only reproduced if proactive auth is disabled, http auth permissions are configured and @RolesAllowed is used for fine grain roles authorization.
Below combinations doesn't reproduce the problem and works fine for all types of resources.
proactive auth is true, http auth permissions are configured and @RolesAllowed is used
proactive auth is false, http auth permissions are configured but @RolesAllowed is not used
http auth permissions are not configured and @RolesAllowed is used.
Issue is only observed in Quarkus 2.11.0 and above. Works fine in 2.10.x
Expected behavior
Resources with non mutiny types should return a successful response
Actual behavior
Resources with non mutiny types are not resolved and requests timesout
Describe the bug
Hi,
Please help me to understand if this is expected behaviour or a bug.
When I configure
quarkus.http.auth.permission.*
andquarkus.http.auth.proactive=false
in a reactive-routes application, Quarkus is not resolving resource methods returning non mutiny types.e.g.
with below config
following resources are not resolved and clients will eventually timeout.
where as below resource works fine.
Issue is only reproduced if proactive auth is disabled, http auth permissions are configured and @RolesAllowed is used for fine grain roles authorization.
Below combinations doesn't reproduce the problem and works fine for all types of resources.
Issue is only observed in Quarkus 2.11.0 and above. Works fine in 2.10.x
Expected behavior
Resources with non mutiny types should return a successful response
Actual behavior
Resources with non mutiny types are not resolved and requests timesout
How to Reproduce?
Reproducer: https://github.com/mvmandapati/reactive-routes
Run
mvn clean verify
to see the test failures.Output of
uname -a
orver
Windows 10 / Linux
Output of
java -version
OpenJDK Runtime Environment Temurin-17.0.4.1+1 (build 17.0.4.1+1) OpenJDK 64-Bit Server VM Temurin-17.0.4.1+1 (build 17.0.4.1+1, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.11.x or above
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3
Additional information
No response
The text was updated successfully, but these errors were encountered: