Hi Clement,
That doesnt help me I need to sync the hash from my source LDAP. Regards, - Ben From: Clément OUDOT [mailto:[email protected]] Sent: 07 November 2013 09:13 To: Benjamin Vogt Cc: Sébastien Bahloul; lsc-users Subject: Re: [lsc-users] unicodePwd :: double colon 2013/11/6 Benjamin Vogt <[email protected]> Hi Sebastien, When I set binaryAttributes and provide the Base64 encoded value, it does not use double colon: changetype: modify replace: unicodePwd unicodePwd: 2rKe+ZA8fFQr+AvgM7KOkw== (The above should be sent with double colons and everything would work) ldbsearch lookup -> unicodePwd: 2rKe+ZA8fFQr+Avg When I set binaryAttributes and provide the Binary string, it uses double colons, but modifies the contents which makes it unusable for AD: changetype: modify replace: unicodePwd unicodePwd:: 2rLvv73vv708fFQr77+9C++/vTPvv73vv73vv70= ldbsearch lookup -> unicodePwd:: 2rLvv73vv708fFQr77+9Cw== You should not encode yourself the value in base64. Just use the LSC method AD.getUnicodePwd(). Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
