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

Skip to content

Conversation

@pedroigor
Copy link
Contributor

@pedroigor pedroigor commented Mar 1, 2024

Closes #20736

  • Introduces a Fetch Roles setting to the role policy to allow checking for any role associated with the user. Otherwise, only roles available from the token that started the authorization request are considered (current behavior)
  • By enabling this option, clients can now leverage lightweight access tokens (as a subject token) because they are no longer forced to map roles to tokens.

jonkoops
jonkoops previously approved these changes Mar 1, 2024
jonkoops
jonkoops previously approved these changes Mar 1, 2024
@pedroigor
Copy link
Contributor Author

@jonkoops Solving conflicts. @jonkoops Could you please re-approve?

@mposolda Would you mind reviewing and merging?

@mposolda mposolda merged commit d12711e into keycloak:main Mar 5, 2024
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.

uma-ticket returns 403 even though user has access, when User Realm Role isn't present in access Token

3 participants