8000 Resolve Audience: Different Audience in ID Token and Access Token · keycloak keycloak · Discussion #14398 · GitHub
[go: up one dir, main page]

Skip to content
Discussion optio 8000 ns

You must be logged in to vote

If the access token actually contains the client ID of a completely uninvolved client (here: "account"), this looks like a misconfiguration or a bug.

The OAuth use case of the access token is not primarily that the frontend client (which triggered the authentication, which is in the azp claim) can check the user identity (that is what the ID token is for!). Rather, the purpose of the access token is to use it when calling a 3rd party API. This 3rd party then checks whether it itself is entered as an addressee in the aud claim.

So you really only need the audience mapper for clients that use the access token in such a 3rd party delgation scenario.

Replies: 4 comments 16 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@sschu
Comment options

sschu Sep 15, 2022
Collaborator

Comment options

You must be logged in to vote
15 replies
@sschu
Comment options

sschu Sep 15, 2022
Collaborator

@sschu
Comment options

sschu Sep 15, 2022
Collaborator

@Zacherl
Comment options

@ceng-p
Comment options

@sschu
Comment options

sschu Mar 13, 2025
Collaborator

Answer selected by Zacherl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants
0