Hi Rolland, I think we have a problem with the database. We will continue the investigations in this direction. Thank you for the help you have given us in supporting the diagnosis. Best regards Pascal
Roland Gruber <[email protected]> le vendredi 12 septembre 2014 à 18:00 +0200 a écrit: >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. ------------------------------------------------------------------------------ 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
