[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Implementing password policy

To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
Subject: Re: Implementing password policy
From: Laurent CARON <lcaron@unix-scripts.info>
Date: Sat, 07 Jan 2012 12:29:59 +0100
Cc: Chris Jacobs <Chris.Jacobs@apollogrp.edu>
In-reply-to: <6C447584419BFE4E83D46E88F81314868A9075D7ED@EXCH07-05.apollogrp.edu>
References: <4F0751EF.3030401@unix-scripts.info> <6C447584419BFE4E83D46E88F81314868A9075D7ED@EXCH07-05.apollogrp.edu>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15pre) Gecko/20110207 Shredder/3.1.9pre

On 06/01/2012 21:29, Chris Jacobs wrote:

Your example shows only 2 pwdFailureTime entries and your policy indicates "pwdMaxFailure: 3".


Hi Chris,

No matter how many failed attempts I make, it never appears as locked:

I now have:
pwdFailureTime: 20120106193928Z
pwdFailureTime: 20120106194040Z
pwdFailureTime: 20120107112658Z
pwdFailureTime: 20120107112705Z

and still no pwdAccountLockedTime.

Is anybody observing the same behavior ?

Follow-Ups:
- RE: Implementing password policy
  - From: Joe Friedeggs <friedeggs44@hotmail.com>

References:
- Implementing password policy
  - From: Laurent CARON <lcaron@unix-scripts.info>
- RE: Implementing password policy
  - From: Chris Jacobs <Chris.Jacobs@apollogrp.edu>

Prev by Date: OpenLDAP 2.4.28 RPMs for CentOS 5 and CentOS 6
Next by Date: RE: Implementing password policy
Index(es):
- Chronological
- Thread