directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "CG Monroe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1774) "Cannot verify the quality of the non-cleartext passwords" error
Date Fri, 07 Dec 2012 14:55:22 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526422#comment-13526422
] 

CG Monroe commented on DIRSERVER-1774:
--------------------------------------

I've had that same problem with password validation.  The solution indicated is the correct
one... although I like to use 1 instead of 0.

That error indicates that you are putting the attribute in the wrong object/location.  The
attached screen shot indicates the correct location.

Also, you will not need to add the attribute.  It should already exist in the config settings
and all you need to do is to modify it.
                
> "Cannot verify the quality of the non-cleartext passwords" error
> ----------------------------------------------------------------
>
>                 Key: DIRSERVER-1774
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1774
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, ldap, schema
>    Affects Versions: 2.0.0-M8
>         Environment: OS : Ubuntu 12.04 64 bit JVM
>            Reporter: Talha KabakuĊŸ
>              Labels: ldap, md5, password, schema, userpassword
>         Attachments: tRoDm.png
>
>
> I'm getting "cannot verify the quality of the non-cleartext passwords" error while trying
to add an entry into my organizationalUnit. I use MD5 hashing method while storing password.
(with userPassword attribute)
> A blog post says the solution is adding ads-pwdcheckquality attribute with value of 0;
but it didn't work for me. And also while trying to add this attribute; it gives a warning
like this:
> http://i.stack.imgur.com/tRoDm.png
> I couldn't find any solution for this issue; so I opened this issue as a "bug".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message