2017-11-01 8:58 GMT+01:00 Nikos Voutsinas <[email protected]>: > Hello, >
Hello Nikos, > Although, I suspect what the answer will be, I thought It might worth asking > here in case someone else has done this before in another not obvious to me > way. > > So, we have a pivotAttribute at the source (ldap) that may hold multiple > values per entry (multivalue ldap attribute) each value is unique across the > result set. At destination the corresponding pivotAttribute holds the same > values in a single form per entry, though. Thus, the source and the > destination entries have a 1-to-N relationship assuming that the connection > key is the pivot Attribute. > > Is there a way, each value coming from the multivalue attribute at the > source to be encountered as a separate entry in the matching process with > corresponding pivot values at destination? The goal here is to sync the > attributes fetched from the source entries to multiple corresponding entries > at destination. I don't see how it could be done with LSC. LSC is designed to map one entry in source to one entry in destination. You can try to create multiple tasks to do this. Clément. _______________________________________________________________ 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
