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
When application with reactive-routes and smallrye-jwt receives invalid token, there is no way to customize response. The issue is valid when proactive security is disabled or enabled.
Expected behavior
My failure handler dealing with AuthenticationFailedException is invoked when JWT token is invalid.
Actual behavior
Exception is caught (event is not failed), default authentication handler is invoked directly, the handler sends a challenge and ends event (iff some auth mechanism didn't end it itself).
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
We discussed multiple solutions here #28391, in PR history can also be found multiple variants of fixes, but it was suggested that it's handled in dedicated issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
When application with
reactive-routes
andsmallrye-jwt
receives invalid token, there is no way to customize response. The issue is valid when proactive security is disabled or enabled.Expected behavior
My failure handler dealing with
AuthenticationFailedException
is invoked when JWT token is invalid.Actual behavior
Exception is caught (event is not failed), default authentication handler is invoked directly, the handler sends a challenge and ends event (iff some auth mechanism didn't end it itself).
How to Reproduce?
Reproducer:
Steps to reproduce the behavior:
git clone https://github.com/michalvavrik/quarkus-reproducer.git
git checkout reactive-routes
mvn quarkus:dev
curl -v "http://localhost:8080/hello" -vvv -H "Authorization: Bearer asdgasdg"
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
We discussed multiple solutions here #28391, in PR history can also be found multiple variants of fixes, but it was suggested that it's handled in dedicated issue.
The text was updated successfully, but these errors were encountered: