You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Frank Brandt (JIRA)" <ji...@apache.org> on 2013/06/05 09:55:19 UTC

[jira] [Comment Edited] (DIRSTUDIO-890) Add support for SSHA2 in Password Editor

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

Frank Brandt edited comment on DIRSTUDIO-890 at 6/5/13 7:53 AM:
----------------------------------------------------------------

The issue is fixed for setting a new password but showing the current password still shows "Unsupported hash method". (see screenshot) I am using Version: 2.0.0.v20130517
                
      was (Author: frank_brandt):
    The issue is fixed for setting a new password but showing the current password still shows "Unsupported hash method". 
                  
> 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-M7 (2.0.0.v20130517)
>
>         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