-
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
Quarkus fails to report a correct exception when conflicting authentication mechanisms are used (was Quarkus: can't verify Auth0 token) #19051
Comments
Hi @cogniocode I've been testing thanks |
@cogniocode And also, please confirm the token which is being sent is a JWT token (you can copy and paste it here if it is a test one or check if it has 3 parts separated by 2 dots - paste it into |
Hi @sberyozkin, thanks for your time. I would love to provide reproducer, if you can tell how to create one :D Here is the token I'm using:
|
@cogniocode Np, this is a JWT token and should be easily verifiable with both The question is how is this stack trace produced - it is not You can create a reproducer by in Github or copy the relevant config here |
The issue was resolved after I have deleted from pom.xml following dependency:
I suppose
|
@cogniocode good it has been resolved - this is a bug that this exception is being triggered - well, we expect it to fail as both extensions provide the same authentication mechanism support for the |
Alright, thanks for your help. |
/cc @pedroigor |
When I add
which is expected. It is the |
Hi, On Quarkus 3.2.0-Final and i have followed this solution here: https://quarkus.io/guides/security-jwt#add-smallrye-jwt |
I fixed this last issue by adding: |
Describe the bug
I have the following OIDC configuration:
While trying to access any endpoint with a valid access token I receive following response:
If logging level is set to DEBUG the following stack trace is printed:
Expected behavior
Quarkus should successfully verify token and give access to endpoint.
Actual behavior
Quarkus throws exception.
How to Reproduce?
Steps to reproduce:
http://localhost:8080/
to allowed callback URLs for the API application.Output of
uname -a
orver
No response
Output of
java -version
11.0.12
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.0.3.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Additional information
No response
The text was updated successfully, but these errors were encountered: