[
https://issues.apache.org/jira/browse/GERONIMO-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated GERONIMO-3876:
----------------------------------
Attachment: GERONIMO-3876.21.patch
Here's a new patch (for branches/2.1) that adds a new JMXSecureConnector that
extends the existing JMXConnector instead of modifying it. I think that's makes
things a bit cleaner. The patch also introduces a new plugin (jmx-security)
that starts the JMXSecureConnector (the plugin depends on the
server-security-config/car and therefore the keystore information will always
be available before this plugin starts - this solves the ordering issue).
I don't see any backwards compatibility issues (for 2.1) with this solution or
even the previous patch where the existing JMXConnector was modified to have
the extra methods.
> Allow configuring JMX over SSL
> ------------------------------
>
> Key: GERONIMO-3876
> URL: https://issues.apache.org/jira/browse/GERONIMO-3876
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: management, security
> Affects Versions: 2.1, 2.1.1, 2.2
> Reporter: Vamsavardhana Reddy
> Assignee: Jarek Gawor
> Fix For: 2.2
>
> Attachments: GERONIMO-3876-B.patch, GERONIMO-3876.21.patch,
> GERONIMO-3876.patch
>
>
> Currently JMX connections to Geronimo or non-SSL and Geronimo does not
> provide configuring SSL for JMX connections. It may be useful to provide
> configuration for JMX connections over SSL.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
