Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@graziang
Copy link
Contributor

@graziang graziang commented Feb 14, 2025

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 audience parameter 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

Copy link
Contributor

@mposolda mposolda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@graziang LGTM, Thanks!

Copy link
Contributor

@rmartinc rmartinc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mposolda mposolda merged commit b4f14b2 into keycloak:main Feb 14, 2025
78 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Filter scopes for token-exchange based on audience and client roles

3 participants