[Date Prev][Date Next]
Re: (ITS#6238) contrib: lastbind overlay to record timestamp of last successful bind
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#6238) contrib: lastbind overlay to record timestamp of last successful bind
- From: Kurt@OpenLDAP.org
- Date: Fri, 10 Dec 2010 18:58:24 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
On Dec 10, 2010, at 10:37 AM, firstname.lastname@example.org wrote:
> On 10/12/10 17:14, Howard Chu wrote:
>> email@example.com wrote:
>>> On 30/07/09 13:50, firstname.lastname@example.org wrote:
>>>> Full_Name: Jonathan Clarke
>>>> Version: RE24
>>>> Submission from: (NULL) (220.127.116.11)
>>>> Please find, at the above URL, an overlay, built for OpenLDAP 2.4, =
>>>> intercepts successful binds and records the current timestamp in an
>>>> named "bindTimestamp" in the bound-to entry. It's original use-case
>>>> is to detect
>>>> unused accounts.
>>>> A configuration parameter (olcLastBindPrecision) allows to set a =
>>>> precision for the timestamp (ie, don't update the timestamp unless
>>>> it's older
>>>> than<n> seconds). This avoids a performance hit from many
>>>> unnecessary writes in
>>>> case there are many binds per minute/hour/day/week/etc.
>>>> Of course, the behaviour this overlay implements is not described =
>>>> any RFC, or
>>>> other. However, it closely resembles some of the functionality from
>>>> the password
>>>> policy overlay, and similar functionality already exists in other
>>>> LDAP servers.
>> There is an equivalent attribute defined in the latest ppolicy draft.
>> Perhaps you could use that.
That attribute is last successful password authentication, not last =
authentication by any means.
For the latter, I suggest a separate attribute. At Isode, we use an =
authTimestamp dsaOperational attribute for this.
It's wise to have the updating of this attribute off by default.
>> Or just submit a patch to incorporate this
>> feature into the current ppoloicy overlay.
> Indeed. At the time I wrote this overlay, I think the ppolicy draft =
> not yet finished or at least I wasn't aware of it. My client at the =
> found it useful to just add this simple overlay, without worrying =
> configuring ppolicy.
> Since then, I actually haven't had any time to work on this overlay, =
> today Michael expressed an interest in it, asking for a public IPR
> notice, thus the "thread revival".
> I hope to pick it up in the future, and at that point possibly submit =
> patch for ppolicy also, as you suggest.