when trying to change passwords programmatically.
I referred him to the password rules in the default policy i.e. the usual:
Passwords may not contain the user's samAccountName (Account Name) value or entire displayName (Full Name value). Both checks are not case sensitive.
The password contains characters from three of the following categories:
- Uppercase letters of European languages (A through Z, with diacritic marks, Greek and Cyrillic characters)
- Lowercase letters of European languages (a through z, sharp-s, with diacritic marks, Greek and Cyrillic characters)
- Base 10 digits (0 through 9)
- Non-alphanumeric characters (special characters) (for example, !, $, #, %)
But there is also another constraint - by default you cannot change your password more than once a day.
This was the reason that was tripping the customer up.
The moral of the story is that if the error says "Password constraint" it's because there is one :-)
You may be wondering how to handle the case where you register a new user programmatically. Normally you create a temporary password and send this in an email and the user clicks on a link which takes them to some kind of "Change Password" page.
The user then changes their password.
In this case, the password is being changed twice so how do you get around the constraint?
Add the "User must change the password at next logon" flag when you create the temporary password.