[jira] [Updated] (AMQ-5753) Not possible to use custom truststore via org.apache.activemq.jndi.ActiveMQInitialContextFactory (within a WebLogic Foreign Server)

["Bernhard Trummer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bernhard Trummer updated AMQ-5753:
----------------------------------
    Summary: Not possible to use custom truststore via org.apache.activemq.jndi.ActiveMQInitialContextFactory (within a WebLogic Foreign Server)  (was: No possibility to use custom truststore via org.apache.activemq.jndi.ActiveMQInitialContextFactory (via WebLogic Foreign Server))

> Not possible to use custom truststore via org.apache.activemq.jndi.ActiveMQInitialContextFactory (within a WebLogic Foreign Server)
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-5753
>                 URL: https://issues.apache.org/jira/browse/AMQ-5753
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.8.0
>            Reporter: Bernhard Trummer
>         Attachments: activemq-client.diff
>
>
> In our WebLogic integration we use a JMS Foreign Server using org.apache.activemq.jndi.ActiveMQInitialContextFactory. When using an SSL connection, then the activemq-client will only "see" the trust store specified with the JVM option -Djavax.net.ssl.trustStore.
> There's no way to specify a custom trust store (and key store) via the initial context properties.
> See attached patch, where I added this feature (based on 5.8.0 release). In order to specify a custom trust store, add the following properties to the initial context:
> - ssl.trustStore=/path/to/broker.ts
> - ssl.trustStorePassword=password
> I can confirm that this patch works with ApacheMQ 5.8.0 and WebLogic 10.3.6.0. I also added properties for ssl.keyStore and ssl.keyStorePassword, but I didn't test connecting with SSL client certificates yet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)