-
Notifications
You must be signed in to change notification settings - Fork 150
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
PoC for Keycloak 23.0.x support #952
PoC for Keycloak 23.0.x support #952
Conversation
Signed-off-by: Thomas Darimont <[email protected]>
- Keep backwards compatibility with Keycloak 18 / RH-SSO - add generated master realm for 23.0.0 - Adapted UserProfile handling to changes in Keycloak 23 - Adapted Groups handling due to changes in Keycloak 23 Needed to Adapt the ImportGroupsIT due to changes in serialization, instead of empty lists or maps, Keycloak now returns null. Fixes adorsys#948
a5131e8
to
c2e80b0
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Note that we are also affected by this regression in Keyclaok 23.0.0 |
@@ -239,4 +238,12 @@ private GroupResource getResourceById(String realmName, String groupId) { | |||
.groups() | |||
.group(groupId); | |||
} | |||
|
|||
public List<GroupRepresentation> getSubGroups(String realmName, String parentGroupId) { | |||
// TODO make max size configurable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use subGroupCount from parent group as max
We are also affected by this: |
Closing in favor of the more complete solution: #958 |
WIP Add Keycloak 23
Needed to Adapt the ImportGroupsIT due to changes in Keycloaks representations,
instead of empty lists or maps, Keycloak now returns null.
This is WIP other behaviour changed as well.
Currently 391 of 442 tests passes (50 failed tests)
Fixes #948
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR