-
I have a quarkus app with quarkus.oidc installed/enabled. Also setup an keycloak and everything is working perfectly fine so far. in my application.properties I have added: Unfortunatly the whole oidc-access-token verification can easily get bypassed by simply removing the "Authorization"-header from the requests. What is the proper way to solve this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
/cc @pedroigor, @sberyozkin |
Beta Was this translation helpful? Give feedback.
-
Found the solution by myself. I had to add following to my application properties: quarkus.http.auth.permission.authenticated.paths=/* |
Beta Was this translation helpful? Give feedback.
-
@charma Right, if the endpoint is public then the token will be still verified due to the proactive authentication which can be disabled but to protect the endpoint one needs to have it requiring the authentication at least, with the path based config as you did or with |
Beta Was this translation helpful? Give feedback.
Found the solution by myself. I had to add following to my application properties:
quarkus.http.auth.permission.authenticated.paths=/*
quarkus.http.auth.permission.authenticated.policy=authenticated