-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group operations broken for Keycloak v23.0.0 #75
Comments
Hey @MrDeerly thanks for the report I guess I can schedule it for next week :) |
Hey @klg71, any chance that you can schedule this soonish? :) |
Hey @MrDeerly I looked into the issue. I would like to update directly to 24. They changed some apis and there is an issue with custom user attributes. |
v24 is fine, lets skip 23 |
I built a release candidate for keycloak 24: https://github.com/mayope/keycloakmigration/releases/tag/0.2.56.RC3. |
Just successfully tested 0.2.56.RC3 with keycloak 24 and 25. As mentioned in the release notes, I had to set the attribute policy manually. For our test setup, we can run the following migration in the first step to update the master realm first and create test realm afterwards - including the attribute policy: ...
changes:
- updateRealm:
id: master
unmanagedAttributePolicy: ADMIN_EDIT
- addRealm:
name: ${REALM}
- updateRealm:
id: ${REALM}
unmanagedAttributePolicy: ADMIN_EDIT Thank you @klg71 for this great tool. When do you plan to release a production version for Keycloak 24/25? |
If you don't have further remarks I will gladly promote the RC to production :) |
Nothing further from my side, looking forward to upgrading. |
Hey!
It seems like group operations like "assignRoleToGroup" are broken when using the current Keycloak version. They seem to have changed their scheme so that subGroups are no longer part of the original group but must be fetched seperatly.
The related changes can be found here:
To get the subGroups of a group
GET /admin/realms/{realm}/groups/{id}/children
must be perfomed. (see https://www.keycloak.org/docs-api/23.0.1/rest-api/index.html)Is there any chance you could look into that soon?
Thanks in advance!
The text was updated successfully, but these errors were encountered: