Le 03/02/2016 13:30, Patrice M. a écrit :
Merci beaucoup Clément!
I'll encounter this problem only on the DIT synchrnization task, so
there are very few attributes I can handle.
Tried the integration of the entryDN pivot attribute, but LSC seems
not to find any source object. As I get as many errors as there are
entries, the culprint id the getOneFilter line.
So, How can I hoandle the "entryDN" parameter?
- I tried <string>dn</string> in <pivotAttributes>, as well as
<string>entryDN</string>
- In addition, in getOneFilter: <![CDATA[(&(dn={dn}))]]> or
<![CDATA[(&(dn={entryDN}))]]>
Without gaining any positive results.
entryDN is an operational attribute available in OpenLDAP.
If this is your diectory server, then you should be able to use it in
pivot attributes and then in filter with entryDN={entryDN}.
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
