Repository navigation
fix: allow to not delete memberships during synchro if the information is not present in LDAP - EXO-87414 - #136
Merged
Merged
Conversation
…n is not present in LDAP - EXO-87414 Sometimes in LDAP, the user membership are not store in 2-directions (group to user with member attribute AND user to group with memberOf attribute) but only in one direction (group to user OR user to group). In this case, when synchronizing it, membership can be removed in exo : If it is stored in group-to-user direction, when you synchronize the user, membership are not seen and then removed in exo. If it is stored in user-to-group direction, when you synchronize the group, membership are not seen and then removed in exo. This commit add 2 properties to be able to not delete the membership is not present in user or group object exo.idm.externalStore.user.memberships.update.delete exo.idm.externalStore.group.memberships.update.delete In addition, the commit ensure to correctly use this attribute to ignore membership which are not present it the attribute is true
rdenarie
enabled auto-merge (rebase)
June 15, 2026 07:20
|
Jihed525
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes in LDAP, the user membership are not store in 2-directions (group to user with member attribute AND user to group with memberOf attribute) but only in one direction (group to user OR user to group). In this case, when synchronizing it, membership can be removed in exo : If it is stored in group-to-user direction, when you synchronize the user, membership are not seen and then removed in exo. If it is stored in user-to-group direction, when you synchronize the group, membership are not seen and then removed in exo.
This commit add 2 properties to be able to not delete the membership is not present in user or group object exo.idm.externalStore.user.memberships.update.delete exo.idm.externalStore.group.memberships.update.delete
In addition, the commit ensure to correctly use this attribute to ignore membership which are not present it the attribute is true