[
https://issues.apache.org/jira/browse/AMQ-9857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated AMQ-9857:
--------------------------------------
Description:
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:
{code:java}
<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> {code}
was:
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.
> ManagementContext should support sslContext injection
> -----------------------------------------------------
>
> Key: AMQ-9857
> URL: https://issues.apache.org/jira/browse/AMQ-9857
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMX
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 6.3.0
>
>
> 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:
> {code:java}
> <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> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
