Hi Roland, Roland Gruber <[email protected]> le jeudi 11 septembre 2014 à 22:30 +0200 a écrit: >then this is no problem with the password hashing. Your accounts are >locked by PPolicy or some other reason. Ok, i check again on that side. > >Try to bind with one of the LDAP command line tools (e.g. >ldapsearch/ldapwhoami) using an affected account. Is the password >accepted here? "normal account" :: ldapwhoami -vvv -h 127.0.0.1-D uid = alam1, ou = users, dc = organization.fr, dc = local -x w nsh67yAB ldap_initialize (ldap: //127.0.0.1) dn: uid = alam1, ou = users, dc = organization.fr, dc = local Result: Success (0)
"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) Thank you for your help. Pascal ------------------------------------------------------------------------------ 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
