[
https://issues.apache.org/jira/browse/ARTEMIS-2961?focusedWorklogId=510882&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-510882
]
ASF GitHub Bot logged work on ARTEMIS-2961:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Nov/20 16:06
Start Date: 12/Nov/20 16:06
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #3332:
URL: https://github.com/apache/activemq-artemis/pull/3332
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 510882)
Time Spent: 20m (was: 10m)
> Configuration SSL/TLS - no way to "reset" password with forceSSLParameters
> --------------------------------------------------------------------------
>
> Key: ARTEMIS-2961
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2961
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: API
> Affects Versions: 2.16.0
> Reporter: Ingemar Allqvist
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I'm a bit stuck here.
> We're using the client, through JCA, in an application server. The
> application has a number of TLS connections, including the connection to the
> artemis broker.
> The issue is, that we use a couple of different trust stores. Some has
> passwords, some don't.
> The "default", "javax.net.ssl.trustStorePassword" has a password (serving som
> SOAP and REST connections), while the trust store used in the broker
> connection don't.
> I can't figure out how to set the broker connections' password to null.
> ForceSSLParameters doesn't help, well, i have no "trustStorePassword" to
> provide, it must be null - otherwise the trust store is "tampered with" when
> the application server tries to connect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)