Thank you very much Clément, it's working as expected now ! So if a "mainIdentifier" exrepssion is defined, LSC will always try to use it and thus rename entries if necessary ? But if it's void, only pivot are considered ?
2013/10/22 Clément OUDOT <[email protected]> > > > > 2013/10/22 SB MK <[email protected]> > >> Thanks for your quick reply. I have already tried this, it's always the >> same. On the source setup, I restricted the selection in the "getAllFilter" >> so that I only have one record to process, debug is a lot quicker ! >> >> So, with both flavours, if I use the '-n" switch, i get : >> oct. 22 17:04:40 - INFO - All entries: 1, to modify entries: 1, >> successfully modified entries: 0, errors: 0 >> >> And when I try to run it for real : >> oct. 22 17:05:14 - INFO - All entries: 1, to modify entries: 0, >> successfully modified entries: 0, errors: 0 >> >> If I remove the condition preventing LSC from changing IDs, he tries to >> modrdn things when running. >> >> dn:xxxxxxx >> changetype: modrdn >> newrdn: attr1=xxxxxxx >> deleteoldrdn: 1 >> newsuperior: >> >> Should I tweak something in the "mainIdentifier" declaration ? >> >> > > Yes, the update cannot be done because LSC wants to rename the entry first. > > > Use <mainIdentifier>""</mainIdentifier> to avoid this. > > > Clément. > >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
