At the following link you may find a working version of the previous posted lsc.xml, in case anyone needs it. The few changes that were required to deal with the problem are accompanied by short notes/comments that explain what's the situation.
http://users.uoa.gr/~nvoutsin/lsc-userpassword-ds2db.working.config.tgz On Tue, Oct 31, 2017 at 3:29 AM, Nikos Voutsinas <[email protected]> wrote: > Besides the fake entries of "requestsNameForDelete" and > "requestsNameForInsert" -and their corresponding entries in iBatis sql > mapping-, also the "createValues" and "defaultValues" were required in the > dataset structure of lsc.xml. Also, the attribute name that is used by the > dataset, should follow the lowercase format of iBatis parameters in the sql > statements. Finally, yes the binary to string transformation is required > when an octet string coming from the ldap should be stored in a database. > > Thank you Clément, > > Nikos > > > On Mon, 30 Oct 2017 at 19:17, Clément OUDOT <[email protected]> wrote: > >> 2017-10-30 15:55 GMT+01:00 Nikos Voutsinas <[email protected]>: >> > Clément, here are the config files, and the debug output from a single >> run: >> > >> > http://users.uoa.gr/~nvoutsin/lsc-userpassword-ds2db.config.tgz >> >> >> I'm not sure this is the reason, but I think you must define a value >> for requestsNameForInsert and requestsNameForDelete in lsc.xml. You >> can map them to dummy SQL request in iBastis configuration. >> >> 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 > >
_______________________________________________________________ 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
