activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3822) The current sslContext element does not provide the ability to define the keystore key password key.
Date Fri, 04 May 2012 12:24:49 GMT

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

Timothy Bish commented on AMQ-3822:
-----------------------------------

Patch applied, moved things around a bit in the test directory to match the current separation
of configs 
                
> The current sslContext element does not provide the ability to define the keystore key
password key.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3822
>                 URL: https://issues.apache.org/jira/browse/AMQ-3822
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: All
>            Reporter: Claudio Corsi
>            Priority: Trivial
>              Labels: activemq, sslContext
>             Fix For: 5.x
>
>         Attachments: client.ts, keystore.ks, sslcontext.diffs
>
>
> The current use of the sslContext element does not provide the ability to use a keystore
that requires two separate passwords, one for the store password and another for the key password.
> This ticket is being created to include another attribute of the sslContext element that
you can use to define the keystore key password.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message