[
https://issues.apache.org/jira/browse/ARTEMIS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204514#comment-15204514
]
ASF GitHub Bot commented on ARTEMIS-445:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/426
ARTEMIS-445 avoid NPE on null ks password
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-445
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/426.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #426
----
commit 8cab6e9d5c00a47a4323d9cd3ccc620f25fff93d
Author: jbertram <jbert...@apache.org>
Date: 2016-03-21T16:07:29Z
ARTEMIS-445 avoid NPE on null ks password
----
> 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)
