[
https://issues.apache.org/jira/browse/KARAF-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055107#comment-13055107
]
Dan Tran commented on KARAF-541:
--------------------------------
Hi Jean, If you dont mind I would like to continue the discussion to get more
exposure from the dev environment.
For my case, with my patch, I create a new karaf management bundle ( call it
2.2.1.1 ), and replace the original one under karaf/system. It works like a
charm.
The draw back, is I have to use <jass:config> to create my own keystore and
trustore right in management bundle. This is the remaining issue i need to
solve before I can ask for Karaf dev team to accept this patch.
For now, the workaround works for me, I just need to get this officially
accepted.
> Support JMX SSL via etc/org.apache.karaf.management.cfg
> --------------------------------------------------------
>
> Key: KARAF-541
> URL: https://issues.apache.org/jira/browse/KARAF-541
> Project: Karaf
> Issue Type: New Feature
> Components: runtime
> Affects Versions: 2.2.0
> Environment: windows, linux, java 6
> Reporter: Dan Tran
> Fix For: 3.0.0
>
> Attachments: KARAF-541-initial.diff, KARAF-541.diff, dps-JMX.zip,
> org.apache.karaf.management.zip
>
>
> Initial discussion is at
> http://karaf.922171.n3.nabble.com/How-to-configure-JMX-connection-with-SSL-td2746251.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
