You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note that attributes can be retrieved using get_group_by_path('/parent'), but they should be in get_groups too - especially since they are in subGroups!
The text was updated successfully, but these errors were encountered:
This is expected based on the default parameters given by the Keycloak's admin REST API, see https://www.keycloak.org/docs-api/latest/rest-api/index.html#_groups. The GET /admin/realms/{realm}/groups has briefRepresentation set to true by default, while GET /admin/realms/{realm}/groups/{group-id}/children has the briefRepresentation set to false by default. Not sure why this is the convention the Keycloak team went for, I guess that'd be a fair question to ask them.
You should be able to get all attributes by calling .get_groups(query={"briefRepresentation": "false"}). We can add this as a default into the library for consistency.
reproduced with v4.1.0 and older versions
When calling admin.get_groups, the parent group attributes are missing.
attributes are present in subgroups, but not in parent group
For instance with the parent group "parent" containing attributes the response will be like:
[ { "id": "parent", "name": "parent", "path": "/parent", "subGroupCount": 1, "subGroups": [ { "id": "child", "name": "child", "path": "/parent/child", "parentId": "parent", "subGroupCount": 0, "subGroups": [], "attributes": {}, "realmRoles": [], "clientRoles": {}, "access": { "view": true, "viewMembers": true, "manageMembers": true, "manage": true, "manageMembership": true } } ], "access": { "view": true, "viewMembers": true, "manageMembers": true, "manage": true, "manageMembership": true } } ]
Please note that attributes can be retrieved using get_group_by_path('/parent'), but they should be in get_groups too - especially since they are in subGroups!
The text was updated successfully, but these errors were encountered: