Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Sat, 15 Jun 2013 08:21:20 +0000 (UTC)
From: "Frank Brandt (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12637740.1363690243281.119912.1371284480282@arcas>
In-Reply-To: <JIRA.12637740.1363690243281@arcas>
References: <JIRA.12637740.1363690243281@arcas>
Subject: [jira] [Commented] (DIRSTUDIO-890) Add support for SSHA2 in
 Password Editor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Frank Brandt commented on DIRSTUDIO-890:
----------------------------------------

I retested with todays nightly build and now "Current Password" and "New Password" features are working as expected. Thanks for fixing...
                
> Add support for SSHA2 in Password Editor
> ----------------------------------------
>
>                 Key: DIRSTUDIO-890
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-890
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 2.0.0-M5 (2.0.0.v20130131), 2.0.0-M6 (2.0.0.v20130308)
>            Reporter: Frank Brandt
>            Assignee: Pierre-Arnaud Marcelot
>            Priority: Minor
>             Fix For: 2.0.0-M8
>
>         Attachments: current_pwd.jpg
>
>
> Tivoli Directory Server v6.3 supports SSHA2 as algorithm for the userPassword attribute. The Password editor cannot display the attribute correctly like for SSHA.
> Sample of possible value:
> {SSHA512}IQze6hxNHkz2h7GjrUBTBPlTrZvRyCSe76q6BpBc1pPAN5IZ0sS8o9Bj7VuFXbHdAe/tjB1mgdKLwzkVwDdNnrKNSRFxoApyTLhMkMHbwaVghVHkg56KppK/OPCrBQkrggemujHunvt025f9VaWnqOW6fIfuN5RLFlYVb5flDA4=
> In addition 256 and 384 Bit are also supported

--
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