Allow TE for clients with consents approved by the user #37491
Merged
Conversation
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
Close keycloak#37112 Signed-off-by: rmartinc <[email protected]>
9125bcf to
73b9702
Compare
Contributor
Author
|
Rebased and updated because we are all changing the same TE classes. 😄 |
graziang
approved these changes
Feb 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Close #37112
Checking the consents are OK for the requested client scopes. The PR moves some validations from the
getTargetAudienceClientsto thevalidateAudiencein the abstract class because now the consent is different in V1 and V2. The scopes are just checked in protectedvalidateConsentsmethod using the sameTokenManager.verifyConsentStillAvailablethat is used in other places. Test added.