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 2021/08/17 11:35:00 UTC
[jira] [Updated] (ARTEMIS-2932) Configuration of SSL/TLS
[ https://issues.apache.org/jira/browse/ARTEMIS-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-2932:
------------------------------------
Fix Version/s: (was: 2.18.0)
2.19.0
> Configuration of SSL/TLS
> ------------------------
>
> Key: ARTEMIS-2932
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2932
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.14.0
> Environment: Windows 10. The client is actually Oracle Weblogic Server, accessing the artemis broker through JCA, but, as far as I can see, the problem is in the NettyConnector and, thus, general.
> Reporter: Ingemar Allqvist
> Priority: Major
> Fix For: 2.19.0
>
>
> It would be useful, if the settings had a precedence list, according to (priority);
> 1) URI-settings
> 2) org.apache.activemq.ssl.*
> 3) javax.net.ssl.*
> i.e the most specific setting (URI-settings) had priority over the more general settings. Now, however, it's exactly the opposite, javax.net.ssl.* has priority over org.apache.activemq.ssl.* has priority over javax.net.ssl.*, which is not that useful.
> If you need to override some javax.net.ssl.* settings, the only fallback is to put "forceSSLParameters" in the URI, and to provide all the settings in the URI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)