Item12793: rework name clash resolution not to use DNs anymore
Priority: Urgent
Current State: Closed
Released In: n/a
Target Release:
Applies To: Extension
Component: LdapContrib
Branches: trunk
Name clash resolution created a lot of trouble. Whenever a user record moved within the directory thus getting a new DN, will this create a name clash
as the code was assuming these two were referring to different users. Users records are reorganized every now and then, e.g. as part of a person changing the organizational unit.
This actually should not result in the cache thinking the two DNS (former and new one) are referring to a different person. Actually using the DN to
resolve name clashes has been a
very bad idea in the first place. It is totally sufficient to use the login for that, e.g. the
sAMAccountName
attribute.
This attribute won't change for the same person moving around inside the directory as people should still be able to log in after reorganizing the directory structure.
--
MichaelDaum - 18 Mar 2014