[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
current password expiration methods
- To: openldap-software@OpenLDAP.org
- Subject: current password expiration methods
- From: Thomas Simmons <twsnnva@gmail.com>
- Date: Wed, 15 Feb 2006 10:09:42 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=VspQW4EH9yjzIX3VwqJrtIpWPpC6gKhAgzTRAhQ5KWzNSydGD5Dwgfe1E9IqyUl5Khs4VMcyQ8Tejm6cWWW3GE1/7brNJBzgluCXdZh19NSdib0Jrj9h+fPXcCM9DzZt6cD5QDAi8EUzqLgUEgH5GJosk0wYr1Uz/PUvTriGBMY=
- User-agent: Thunderbird 1.5 (Windows/20051201)
Hello,
I would like to get opinions on current methods of handling password expiration and history within LDAP. When
I last checked, I remember something about ppolicy, I believe it had just entered CVS or something... Is this
an acceptable method of achieving the above goals? I assume this question should be pretty straight forward,
but if more info is needed, Let me know. Thanks.
OpenLDAP 2.2.7 (Debian Package)
Thomas Simmons