I dont think you have done your best You have just repeated what is mentioned on your website. You have not provided any solution for the double colon.
I have tested this and IT WORKS. If I push this into AD with ldapmodify, I can login. If I use lsc, I cannot login, because 1) it doesnt use a double colon for base64 encoded string or 2) it modifies the data if I provide binary data I can get the hash in base64, but I need a double colon. I can provide the binary value, but I need lsc not to modify the data. Why can you not explain how to use the setDataset method instead? This should pass the data without modifying anything as opposed to String. - Ben From: Clément OUDOT [mailto:[email protected]] Sent: 07 November 2013 11:36 To: Benjamin Vogt Cc: lsc-userslsc-users Subject: Re: [lsc-users] unicodePwd :: double colon 2013/11/7 Benjamin Vogt <[email protected]> You are talking about oranges and apples. Your solution is not viable, because I do not have the plaintext passwords. The double colon is the magic. Instead of providing me alternatives which do not work in my case, please help me get lsc to use a double colon. I think I have done my best. Good luck. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
