Don’t use entryDN as a pivot. Use an attribute that is unique to each record but common to both copies of the record. In your case the RDN might be a good choice. I’m assuming that’s either UID or CN. You can then do a simple JavaScript substring replace on the entryDN attribute in the <mainIdentifier> element of your LSC job to convert your source DN to a destination DN.
-Jon C. Kidder American Electric Power Middleware Services Email: [email protected]<mailto:[email protected]> Phone: 614-716-4970 From: [email protected] [mailto:[email protected]] On Behalf Of Juan Carlos Camargo Sent: Tuesday, February 10, 2015 6:41 AM To: lsc-userslsc-users Subject: [lsc-users] Dynamic filters This is an EXTERNAL email. STOP. THINK before you CLICK links or OPEN attachments. ________________________________ Hi LSC'ers :) Is there a way to insert scripts in destination filters? The point is, if I could build a <getOneFilter> in destination to match the source, then things would be easier when handling different ldap domains. In my case I'm trying to sync the whole OU (just organizational units) tree from server A to B: * Server A is dc=domainA,dc=org * Server B is dc=domainB,dc=org Pivot is entryDN and it will never be the same , so entries are always treated as new, no matter if they already exist in B. However, if I could use a script then it'd be as easy as replacing the domain in B, kind of <getOneFilter>js:<buildDN>.replace("domainA","domainB") </getoneFilter> or similar. [Image removed by sender.] Tfn: 957-211157 / 650932877
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
