Repository navigation
Replies: 1 comment
|
I finally figured out what was happening after starting to look at the LDAP side more closely. There wasn't anything in the logs that looked out of place but then I went into the Sorry to clutter up the discussions, but as always, as soon as you post, you figure it out. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I'm trying to upgrade my KC instance to v23 (I know that this is an older release but the release cadence is just too quick with often breaking changes to keep up in my environment) but after deploying KC23, when trying to add a user to a group (either using the UI or REST API), the group gets populated correctly in LDAP (a new uniqueMember attribute of the user's UID is created), but the user's account does not get updated with the corresponding
memberOfattribute with the new group. Additionally, if you try to remove a user from a group (i.e. select Leave from the groupsMemberstab, etc), that doesn't remove the user from the group in LDAP at all. I don't see any error in the container logs at all.There doesn't seem to be any fundamental changes regarding the LDAP provider and group mapper configuration between v22 and v23 and I've searched through numerous Issues relating to LDAP to see if this has come up before but I'm struggling to find an explanation as to why this no longer works. Has anyone experienced something like this in their upgrade cycles or aware of a known bug for all 23 versions that might explain why KC is not adding
memberOffor group adds?Thanks for looking.
All reactions