2013/11/29 Matteo Perego <[email protected]> > Il 29/11/2013 11:39, Clément OUDOT ha scritto: > > Hi Clement, > >> with that rule and a getOneFilter like this: >> >> <getOneFilter>(distinguishedName={distinguishedName})</getOneFilter> >> >> I didn't get results on the destination AD cause {distinguishedName} >> seems to be resolved on the SRC main identifier and not the DST one. >> >> Without results LSC try to create an already existing entry. >> >> I cannot use other attributes (like {cn}) cause they're not unique. >> > > > You should use sAMAccountName as pivot, as they should be unique. > > > Clément. > > Hi Clement, > unfortunately contacts doesn't have a samaccountname. I wonder if I can > set the ldap search to be "one level" and not "sub" type as workaround... >
No, you can't change the scope of the search. I think AD should have a technical attribute storing a unique ID. If anyone has an idea? Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
