Hi EJ,

On 07.08.2014 17:05, Elizabeth Jones wrote:
> 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?

LAM puts an "!" after the SSHA. I suggest to use the PPolicy overlay to
lock accounts in your case. This requires to install the PPolicy overlay
on your LDAP server.


-- 

Best regards

Roland


LDAP Account Manager
http://www.ldap-account-manager.org/

Want more? Get LDAP Account Manager Pro!
https://www.ldap-account-manager.org/lamcms/lamPro

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
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

Reply via email to