Configure an optional password message digest algorithm which is applied on userPassword attribute values at add and modify operations.

• Key: DIRSERVER-289
• Type: Improvement
• Status: Reopened
• Priority: Minor
• Assignee: Stefan Zoerner
• Reporter: Alex Karasulu
• Affects Version/s: 1.5.1, 1.5.0, pre-1.0
• Fix Version/s: 2.0.0-RC1

Description

See http://issues.apache.org/jira/browse/DIREVE-296 for more information. This issue is meant to handle extra work on 296 since most of it has already been implemented.

Comments

[Alex Karasulu]

These issues are related. This one is to complete the functionality on DIREVE-296.

[Alex Karasulu]

I think stefan already took care of this one.

[Stefan Zoerner]

The missing part of DIRSERVER-261 ("Storing user passwords other than in clear"), which is called "extra work" in the description, and which this issue is for, has not been implemented yet. Note that it is not critical for 1.0.

[Stefan Zoerner]

I made a mistake with the version numbers during edit.

[Alex Karasulu]

Stefan is this something that is remaining? Shall I push this out to 1.5.1 or do you want to try for 1.5.0?

[Stefan Zoerner]

I would like to implement both http://www.faqs.org/ftp/internet-drafts/draft-behera-ldap-password-policy-09.txt and http://www.faqs.org/rfcs/rfc3112.html. It should be possible with the help of an interceptor. But I will probably not be able to complete this for a near 1.5.0.

So it is appropriate to move this to 1.5.1, I think.

[Alex Karasulu]

moving 2 1.5.1 on req from stefan

FYI, SHA, SSHA, MD5, SMD5 and crypt have been implemented in 1.5.1. This is far from being enough if you consider http://www.faqs.org/ftp/internet-drafts/draft-behera-ldap-password-policy-09.txt and http://www.faqs.org/rfcs/rfc3112.html, but this is a first step.

[Emmanuel Lecharny]

Status ?

Postponed.

[Emmanuel Lecharny]

Postponed to 2.0.0-RC1