[jira] [Commented] (ARTEMIS-2932) Configuration of SSL/TLS

["Robbie Gemmell (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278245#comment-17278245 ] 

Robbie Gemmell commented on ARTEMIS-2932:
-----------------------------------------

A sub-section of this, the system property ordering, has been restored to the desired and original behaviour in ARTEMIS-3081.

> 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
>
> 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)