On 04/06/2019 17:10, Jehan Procaccia wrote: > indeed maybe I wasn't clear enough of what I want to do > > in SRC ldap I have a branch for our school structures (organigram) , > example : > > dn: sn=dsi,sn=tsp,ou=Structures,dc=domain,dc=fr > sn: dsi > cn: Direction Systems Informations > > In the DST ldap I want these structures to take supannCodeEntite as the > rDN (in place of sn) and on the fly change the values from last branch > name to full organigram tree with "/" as separator : > so for example the SRC dsi structure above will be renamed from its DN > tree to : > > dn: supannCodeEntite=tsp/dsi,ou=Structures,dc=domain,dc=fr > supannCodeEntite: tsp/dsi > description: Direction Systems Informations > > is this more clear ? can it be done in a LSC task ? > > Thanks .
Hi, It's more clear. Unfortunately, I don't think you'll be able to do this in just one task, as LSC tries to match entry in sync mode to figure out if it's a creation (no match found in destination for a source entry) or an update (found a match in destination for a source entry), or a delete in clean mode (no match in source for a destination entry). To do this, it uses declared pivot attributes to compose getOneFilter and cleanFilter. Transformation of pivot attributes is not available in 2.1 (it's in store for 2.2). I would address this case like this : - Choose an unused attribute in the source entry ; - Write a synchronization source to source, update only, that write this attribute with the targeted supannCodeEntite (you can script going up the DN to gather information) - Write the main synchronization source to destination that uses this attribute as source pivot in filters and in mainIdentifier ; Hope this help. Regards -- Soisik Froger | Software Architect [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
