Replies: 1 comment 9 replies
-
Thanks @effusion, let me check... I'd like to clarify for everyone that what is described here, and which is what we briefly discussed with @effusion earlier, is the case where both Azure authorization code flow ID and access tokens have to be verified, with these two types of tokens having different issuer and audience claims. The proposed plan has been to set both of these claims to |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
we currently face the issue of not getting Azure Authentication working with
quarkus.oidc.authentication.verify-access-token
set totrue
.Our endpoint looks as follows:
and the OIDC configuration like:
The main problem at the moment is that even if
quarkus.oidc.token.audience
is set toany
, we always get an exception that theaud
claim does not match the expected value. For the propertyquarkus.oidc.token.issuer
the valueany
works. Azure gives out tokens with different claims for id and access token.Thanks to @sberyozkin help, I also found out about the https://quarkus.io/guides/security-oidc-bearer-token-authentication#jose4j-validator to customize claim validation. Unfortunately, this does not prevent the token verification from failing.
Did anyone else face this issues?
Beta Was this translation helpful? Give feedback.
All reactions