Back to bug 1044142

Who When What Removed Added
Nathan Kinder 2013-12-17 21:21:38 UTC Status NEW POST
Noriko Hosoi 2014-06-13 18:54:09 UTC Blocks 1109381
Noriko Hosoi 2014-06-18 00:34:53 UTC CC nhosoi
Doc Text 1)
Problem:
A group on AD has a member which is not a target of windows
sync and exists only on AD. The member value in the group is synchronized to DS. If an operation is executed on AD so that the member is replaced with other members which are the target of the windows sync, the new member values are not synchronized.
Fix:
In windows_generate_update_mods, even if a sync'ed member value in a DS entry is not the target of windows sync and it is does not exist on DS, a following modify operation including the member value is proceeded by confirming the existence on AD.

2)
Problem:
If a group on AD and DS have members which are local and are
not synchronized and the members are removed in the group on
the other side, the delete operation is synchronized and
deletes all the members including the local members.
Fix:
Added the code to check if an attribute is completely deleted on one side, then the each value on the other side is in the sync scope or not. Put the value to the mod for the delete only if the value is in the sync scope.
Noriko Hosoi 2014-09-06 01:04:27 UTC Status POST MODIFIED
Fixed In Version 389-ds-base-1.3.3.1-1.el7
errata-xmlrpc 2014-09-06 01:26:54 UTC Status MODIFIED ON_QA
Jenny Severance 2014-10-23 14:56:03 UTC Priority unspecified medium
Viktor Ashirov 2015-01-17 19:06:34 UTC Status ON_QA VERIFIED
CC vashirov
Viktor Ashirov 2015-02-26 13:01:22 UTC QA Contact sramling vashirov
errata-xmlrpc 2015-03-04 16:05:48 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2015-03-05 09:29:36 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2015-03-05 04:29:36 UTC
Simon Pichugin 2020-09-13 20:14:18 UTC Link ID Github 389ds/389-ds-base/issues/415

Back to bug 1044142