Support nested claim mapping for groups attribute #1149
Merged
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 provider option "Enable nested and fallback claim mappings" recently introduced in #1103 currently doesn't work for the groups attribute mapping since
getSyncGroupsOfTokenuses$groupsAttributefor directly accessing properties inside$idTokenPayload(instead of usinggetClaimValueto allow for dot-notation resolution).This is unfortunate because some identity providers, such as Keycloak, nest user roles inside the ID token (e.g., under
realm_access.rolesfor Keycloak realm-level andresource_access.${client_id}.rolesfor Keycloak client-level roles).My PR fixes the issue by adding the method
getClaimValuesand using it inside ofgetSyncGroupsOfToken.getClaimValuesincludes most of the logic ofgetClaimValue, but allows returning non-string values. The original behavior ofgetClaimValueis retained.Closes #799.