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

Re: to anyone who uses slapo-lastbind on their ldap server

To: curious penguin <pepe.the.bofh@gmail.com>
Subject: Re: to anyone who uses slapo-lastbind on their ldap server
From: Turbo Fredriksson <turbo@bayour.com>
Date: Tue, 14 Feb 2012 19:38:45 +0100
In-reply-to: <CADL9bSERuAf2gmJG1qUbCQDPqRba3=jybTvNct=uwWNZS0c_bA@mail.gmail.com>
References: <CADL9bSERuAf2gmJG1qUbCQDPqRba3=jybTvNct=uwWNZS0c_bA@mail.gmail.com>
Resent-date: Tue, 14 Feb 2012 19:39:40 +0100
Resent-from: Turbo Fredriksson <turbo@bayour.com>
Resent-message-id: <201202141840.q1EIe9V8016490@boole.openldap.org>
Resent-to: openldap-technical@openldap.org

On Feb 14, 2012, at 7:07 PM, curious penguin wrote:

The reason why I'm saying it isn't working is I can't see the AuthTimestamp attribute anywhere in my database. Here's an output of slapcat and ldapsearch for your review:

Who told you that you would? To my knowledge, there is no such

attribute (in OpenLDAP).

Try not. Do. Or do not. There is no try!

- Yoda

Follow-Ups:
- Re: to anyone who uses slapo-lastbind on their ldap server
  - From: Howard Chu <hyc@symas.com>

References:
- to anyone who uses slapo-lastbind on their ldap server
  - From: curious penguin <pepe.the.bofh@gmail.com>

Prev by Date: Re: Missing Syntax description in the cn=subschema's LDAPSyntaxes AT
Next by Date: Re: to anyone who uses slapo-lastbind on their ldap server
Index(es):
- Chronological
- Thread