> Hi EJ, > > On 05.08.2014 20:57, Elizabeth Jones wrote: >> The difference is the user on this page is trying to change his password >> from the command line and I'm trying to change through LAM. If the >> answer >> on this web page really is what is happening (the password is being >> hashed >> before getting to my LDAP), where in LAM would I change the setting to >> clear? We are using TLS so the password should be ok between my server >> and the LDAP. > > in your LAM server profile select Module settings and then change the > password hash type to PLAIN. This should solve the issue.
This worked - my servicedesk is now able to create and modify user accounts. However, when they try to lock accounts using the lock password button they are still getting a constraint violation. If I'm remembering correctly, this button adds a 1 to the beginning of the password? I'm wondering if the password doesn't conform to the new password constraints and they try to lock it, its getting rejected because even with 1 in front, if it doesn't conform them it can't save? Or could there be something else going on with the lock password button? thanks, EJ ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
