Hi Benjamin, Try to setup the *binaryAttributes value inside your ldapConnection settings (see * http://lsc-project.org/wiki/documentation/2.0/configuration/connections/ldap<http://lsc-project.org/wiki/documentation/2.0/configuration/connections/ldap?s[]=binary> )
It enforces the use of the binary form of the corresponding attribute. Regards, Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ 2013/11/6 Benjamin Vogt <[email protected]> > Is it possible to get lsc to pass a double colon for unicodePwd? > > > > e.g: > > ---- > > changetype: modify > > replace: unicodePwd > > unicodePwd*::* 2rKe+ZA8fFQr+AvgM7KOkw== > > > > Modified 1 records successfully > > ---- > > > > I need to pass the hash value to the AD server. It works with ldapmodify, > but I do not know how to do it with lsc. Passing the hash with a single > colon makes AD truncate it and the password becomes unusable. > > > > I can however pass the binary representation of the hash, which is much > shorter, and a single colon instead in ldapmodify, however lsc doesn’t like > binary data either. > > > > Regards, > > - Ben > > > > > > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-users mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-users > >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
