jbonofre opened a new issue, #1699:
URL: https://github.com/apache/activemq/issues/1699
If an user wants to use SSL with JMX, the only option today is to configure
via the command line (`-Dcom.sun.management.jmxremote.port=xxxx
-Dcom.sun.management.jmxremote.ssl=true`).
This configuration doesn't use the `sslContext` meaning that the user might
have to duplicate the SSL configuration two times:
- the `sslContext` in `activemq.xml` that can be used in `transportConnector`
- the same configuration via the command line
(`com.sun.management.jmxremote*`)
It would be great to be able to inject the `sslContext` in the
`<managementContext/>` to use an unique configuration.
Something like:
```
<sslContext>
<sslContext id="fooContext"
keyStore="file:./path/broker2.ks" keyStorePassword="password"
trustStore="file:./path/client2.ks" trustStorePassword="password"/>
</sslContext>
<managementContext>
<managementContext createConnector="true" sslContext="#fooContext"/>
</managementContext>
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
