Hi Pascal, On 12.09.2014 10:33, PASCAL CASSAGNES wrote: > "affected account" : > ldapwhoami -vvv -h 127.0.0.1-D uid = alam4, ou = users, dc = > organization.fr, dc = loca l-x w NBHU4tGH > ldap_initialize (ldap: //127.0.0.1) > ldap_bind: Invalid credentials (49)
in this case there are only a few possibilities: * account locked by PPolicy if you use this (can be checked with LAM's PPolicy user module) e.g. because of too many failed login attempts * some other server side overlay * master-slave replication problem * database corruption You can also try to debug the LDAP server why it reports invalid credentials while the password hash is ok. See end of this page: https://www.ldap-account-manager.org/static/doc/manual/api.html But this seems to be no LAM problem. -- 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
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
