Le 17/10/2018 à 14:52, twikk a écrit : > Hello, > > The JS in the dataset is not really a problem to implement, but the source > logic is (each entry found is mapped and I don't want that in this specific > case). > > Maybe I don't understand well the process but how can find the objects in the > source and force the destination attributes/objects to be only executed > through JS and not the default logic (each entry mapped, etc.).
You must map entries, but you can have only one entry in source, which is the "ou=xxx" branch, by configuring search base and filter. For example: <baseDn>ou=xxx,dc=example,dc=com</baseDn> <getAllFilter><![CDATA[(&(objectClass=organizationalUnit)(ou=xxx))]]></getAllFilter> Then use javascript with "srcLdap" to get all values you want to put in destination. -- Clément Oudot | Identity Solutions Manager [email protected] Worteks | https://www.worteks.com _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
