OK, got the gist of bin2string, however just by putting the dataset element within the task, I get an NPE, no matter what the dataset is trying to do, ie even when the following is used
<dataset> <name>userPassword</name> <policy>FORCE</policy> <forceValues><string>""</string></forceValues> </dataset> That seems to me like side effect caused by the LDAP-2-DB flow. FYI, the actual value at the source is read correctly by LSC, considering the ldif that LSC outputs on the console. On Mon, Oct 30, 2017 at 12:01 PM, Clément OUDOT <[email protected]> wrote: > 2017-10-30 10:46 GMT+01:00 Nikos Voutsinas <[email protected]>: > > Hello Clément, > > > > I've set the userPassword as binaryAttribute in lsc.xml, however nothing > > changed. > > Ok, remove userPassword from binaryAttributes and try this javascript > in your dataset to get the String value: > > var octetString = srcBean.getDatasetFirstValueById(" > userPassword"); > var str = java.lang.String(octetString); > > > 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
