This behaviour was observed in an oneWaySync: fromWindows setup

This could be the same problem like #47642

Replying to [comment:6 cgrzemba]:

This could be the same problem like #47642

We've released 389-ds-base-1.3.1.19 on F19 and 1.3.2.13 on F20 for testing.
http://directory.fedoraproject.org/wiki/Releases/1.3.2.13
http://directory.fedoraproject.org/wiki/Releases/1.3.1.19
If you could try one of them and update us with the result, we'd appreciate it.

Replying to [ticket:47408 cgrzemba]:

If a user is moved from one OU to an other OU on AD (DN change), than it will also moved on LDAP, correct.
But if the user member of a already synced group, than the uniquemember attribute in the LDAP Group will not changed. The old DN still remains in the uniquemember attribute.

I verified this scenario works. The renamed member in the already synced group is replaced with the new DN.

Closing this bug as a duplicate of #47642. Please feel free to reopen it with the reproducer steps if you run into a problem.

Thanks!

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/745

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.