Repository navigation
Support for managing members via group resource type - #47636
Conversation
There was a problem hiding this comment.
Thanks @pedroigor for the PR, I noticed we will have to also add permission checks before we proceed to joining or leaving groups for users.
I have a #47616 addressing exactly this from the user side of the relationship.
|
@vramik I'll wait for your PR. |
There was a problem hiding this comment.
If I got this right, nothing is calling the ScimJsonNodeFilterEvaluator anymore. Even Path.getValue() doesn't seem to be used anymore. If that's the case, can't we remove these things?
04d7bd7 to
a1478f7
Compare
@sguilhen Yeah, the |
|
@vramik Access checks updated to |
There was a problem hiding this comment.
@pedroigor thanks, I see the permissions are correctly applied.
I have two questions:
- how do we aim to handle organization groups in SCIM endpoints?
- I purposely blocked the access in my PR, see
UserCoreModelSchema.checkGroupMembershipPermission, when looking atGroupResourceTypeProvider.getGroupPredicatesit does filter out org groups -> we should then add a check for org group intoGroupCoreModelSchema
- I purposely blocked the access in my PR, see
- optionally we can introduce small shared utility class, something like
GroupMembershipPermissionswherecheckUserMembershipPermissionandcheckGroupMembershipPermissioncould live.
Closes keycloak#46216 Signed-off-by: Pedro Igor <pigor.craveiro@gmail.com>
8867483 to
97c2be1
Compare
Closes #46216
membersattributeGroup#membersattribute is only returned if requested to avoid fetching all membershipsUser#groupsattribute is only returned if requested to avoid fetching all memberships