Filter scopes in token exchange v2 based on requested audience #37353
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.
Closes #37147
In the case where valid audiences are requested in the standard token exchange v2 request, only the realm roles and client roles belonging to the clients present in the
audienceparameter are considered during the scope evaluation.Also token exchange requests with client scopes that do not exist or are not configured as default or optional for the requester client are rejected.
In all other cases, the behavior remains the same. You can find an example in this comment #37147 (comment).
NOTE: At the time of this PR, audiences are never blocked. The task to block audiences is: #37104