You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/03/21 16:54:25 UTC

[jira] [Assigned] (ARTEMIS-445) Truststore/Keystore password cannot be null although null is an acceptable value

     [ https://issues.apache.org/jira/browse/ARTEMIS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram reassigned ARTEMIS-445:
--------------------------------------

    Assignee: Justin Bertram

> Truststore/Keystore password cannot be null although null is an acceptable value
> --------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-445
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-445
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 1.1.0, 1.2.0
>         Environment: Wildfly 10.0.0.Final
>            Reporter: Dominique Toupin
>            Assignee: Justin Bertram
>            Priority: Minor
>              Labels: newbie
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> It is currently impossible to define a connector with SSL enabled to which the only other piece of information provided is the truststore path. The reason for this is that although the truststore password could be null by definition (java.security.KeyStore.load accept a null value), the code does not check whether the variable keystorePassword is not null before calling toCharArray and therefore we end up with a NullPointerException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)