Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 235532

Summary:	passwordexpirationtime resets to 19700101000000Z when using pam_password exop
Product:	[Retired] 389	Reporter:	Scott Kile <scott.kile>
Component:	Security - Password Policy	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED DUPLICATE	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0.4	CC:	benl, nkinder
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-04-09 17:19:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	249650, 493682

Description Scott Kile 2007-04-06 19:24:52 UTC

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 17:00:43 UTC

Nathan, do you recall if this was fixed in 1.2.0?

Comment 3 Nathan Kinder 2009-04-09 17:08:06 UTC

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 17:19:34 UTC


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