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 2020/11/12 16:15:00 UTC
[jira] [Resolved] (ARTEMIS-2961) Configuration SSL/TLS - no way to
"reset" password with forceSSLParameters
[ https://issues.apache.org/jira/browse/ARTEMIS-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-2961.
-------------------------------------
Fix Version/s: 2.17.0
Resolution: Fixed
> 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
> Fix For: 2.17.0
>
> 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)