[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: OL 2.3.11, pwdChangedTime not updated
- To: openldap <openldap-software@OpenLDAP.org>
- Subject: Re: OL 2.3.11, pwdChangedTime not updated
- From: Samuel Tran <stran@amnh.org>
- Date: Tue, 01 Nov 2005 10:44:30 -0500
- In-reply-to: <1130786909.5484.37.camel@mistral>
- References: <1130786909.5484.37.camel@mistral>
On Mon, 2005-10-31 at 14:28 -0500, Samuel Tran wrote:
> Hi All,
>
> I am using OL 2.3.11 on a Debian Linux 3.1 (Sarge) with the password
> policy overlay.
>
> I noticed somethig strange. Everytime I changed a password for a given
> user the internal attribute, pwdChangedTime doesn't get updated. For
> instance, look at this user joesmith:
>
> dn: uid=joesmith,ou=People,dc=example,dc=com
> pwdPolicySubentry: cn=StdPwd,ou=Policies,dc=example,dc=com
> structuralObjectClass: inetOrgPerson
> entryUUID: 47ee59a2-c886-1029-8066-d7d16b193810
> creatorsName: cn=miis,ou=Accounts,ou=Apps,dc=example,dc=com
> createTimestamp: 20051003182137Z
> pwdChangedTime: 20051003182137Z
> entryCSN: 20051031192002Z#000000#00#000000
> modifiersName: uid=stran,ou=People,dc=example,dc=com
> modifyTimestamp: 20051031192002Z
> entryDN: uid=joesmith,ou=People,dc=example,dc=com
> subschemaSubentry: cn=Subschema
> hasSubordinates: FALSE
>
> pwdChangedTime value is the same as createTimestamp value. It should
> actually have the same value as modifyTimestamp. Is it correct?
>
It was a misconfiguration on my end. It is working as designed.
Sorry for the confusion.
--
Sam