Bug 235532 - passwordexpirationtime resets to 19700101000000Z when using pam_password exop
passwordexpirationtime resets to 19700101000000Z when using pam_password exop
Status: CLOSED DUPLICATE of bug 248924
Product: 389
Classification: Community
Component: Security - Password Policy (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Rich Megginson
Chandrasekar Kannan
Depends On:
Blocks: 249650 FDS1.2.0
  Show dependency treegraph
Reported: 2007-04-06 15:24 EDT by Scott Kile
Modified: 2015-01-04 18:25 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-04-09 13:19:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Scott Kile 2007-04-06 15:24:52 EDT
Description of problem:
Server: fedora-ds-1.0.4-1.FC6.i386
OS RHEL5 Client Workstation
Sun Java 1.5.0_11-b03

When the /etc/ldap.conf pam_password line is set to exop, server configured
password policies (composition and history) work, but the passwordexpirationtime
resets to 19700101000000Z when changing the password with /usr/bin/passwd.

When the pam_password line is set to md5 the passwordexpirationtime is set
properly but server password poilicies are ignored.

How reproducible:
Change /etc/ldap.conf to have "pam_password exop" line.

Setup Password Expiration under Directory Server -> Configuration -> Data ->
Passwords.  Set password to expire after 180 days.

Use /usr/bin/passwd to change a LDAP account password.

Look at the passwordexpirationtime on the changed account.

Thank You
Comment 2 Rich Megginson 2009-04-09 13:00:43 EDT
Nathan, do you recall if this was fixed in 1.2.0?
Comment 3 Nathan Kinder 2009-04-09 13:08:06 EDT
I believe that this was fixed as part of bug #248924.  The fix is in 1.2.0.
Comment 4 Rich Megginson 2009-04-09 13:19:34 EDT

*** This bug has been marked as a duplicate of bug 248924 ***

Note You need to log in before you can comment on or make changes to this bug.