[
https://issues.apache.org/jira/browse/ARTEMIS-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281990#comment-17281990
]
Robbie Gemmell commented on ARTEMIS-2932:
-----------------------------------------
All the changes noted here were not made, perhaps the the key one of having URI
values take most precedence was not, though the system property aspect was.
I dont think it should be resolved agaisnt 2.17.0 as-is due to that, it would
be at best a partial duplicate. ARTEMIS-3081 was already resolved agaisnt
2.17.0 and covers what was changed, so it seems this is either closed as
wont-fix'ing the remaining aspects, or left open for future consideration of
them. In both cases I'd remove the fix-version.
> 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.17.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)
