Issue #55 has been updated by Clément OUDOT.
Status changed from Feedback to Assigned
Assigned to changed from Clément OUDOT to Raphaël Ouazana
Target version changed from 2.1 to Not planned
Tested with 2.1 branch but it does not work.
Test was made by setting directly the accentued value in lsc.xml, inside the
dataset:
<pre>
<dataset>
<name>unicodePwd</name>
<policy>FORCE</policy>
<forceValues>
<string>AD.getUnicodePwd( "Soleil123à" )</string>
</forceValues>
</dataset>
</pre>
I can use this password when I change it directly into AD. Maybe some code to
change in getUnicodePwd method.
----------------------------------------
Bug #55: AD password encoding doesn't support non-ASCII characters
http://tools.lsc-project.org/issues/55
Author: Jonathan Clarke
Status: Assigned
Priority: Low
Assigned to: Raphaël Ouazana
Category: Core
Target version: Not planned
Problem in version:
Thomas found that if a password contains special characters (like "é", "à",
etc.), LSC says that password modification succeed, we cannot authenticate with
this new password. In fact, the old one is still valid :/
It may be a wrong charset used to encode the password. Default charset on
Windows systems is CP1252.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://tools.lsc-project.org/my/account
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev
