Repository navigation
!!! Check the authorized party of every token addressed to the client - #90
Merged
Merged
Conversation
The provider now checks the "azp" claim of every token whose audience contains the client id of the service, also if the "audience" option is set. Access tokens for an API, which other clients obtained, are left alone, because their audience doesn't contain the client id. Previously, the "audience" option switched the check off completely. An application which set it, for example to accept identity tokens and access tokens for its API, accepted identity tokens issued to another client of the same tenant, as long as they also named this client as an audience. This is a behaviour change for applications with an "audience" option: tokens addressed to the client with several audiences and no "azp", or with the "azp" of another client, are now rejected. Addresses: #81
robertlemke
force-pushed
the
feature/azp-per-token
branch
from
October 9, 2026 11:15
5f3d5ac to
81915a4
Compare
robertlemke
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
azpcheck from #88 now applies to every token whose audience contains the client id of the service, instead of being switched off by theaudienceoption. Access tokens for an API, which other clients obtained, stay unaffected, because their audience doesn't contain the client id. Without anaudienceoption nothing changes.This is a behaviour change for applications with an
audienceoption: tokens addressed to the client with several audiences and noazp, or with theazpof another client, are now rejected.Addresses: #81