Issue #55 has been updated by Jonathan Clarke. Target version changed from 1.1.1 to 1.1 branch
There has been no activity on this, and 1.1.1 is going to be released. Retargeting for later in 1.1 branch. Can someone who has access to an AD server confirm this is still broken? ---------------------------------------- Bug #55: AD password encoding doesn't support non-ASCII characters http://tools.lsc-project.org/issues/show/55 Author: Jonathan Clarke Status: New Priority: Normal Assigned to: Category: Core Target version: 1.1 branch 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
_______________________________________________ lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
