[
https://issues.apache.org/jira/browse/KARAF-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512886#comment-15512886
]
Paolo Antinori commented on KARAF-3513:
---------------------------------------
[~ffang] Hi, I don't see commits related to this JIRA
https://issues.apache.org/jira/browse/KARAF-3513 in current 4.x Master
Do you think this is correct?
I'd like to contribute on top of your commits, with this fix:
https://github.com/jboss-fuse/karaf/compare/2.4.0.redhat-6-3-x...paoloantinori:ENTESB-2192_picked?expand=1
that seems to have been already reported here:
https://issues.apache.org/jira/browse/KARAF-3887
Can I ask you to double check if anything is missing or if I'm looking at the
wrong place?
> JMXConnectorServer should be able to pick up the new KeystoreInstance
> available in container
> --------------------------------------------------------------------------------------------
>
> Key: KARAF-3513
> URL: https://issues.apache.org/jira/browse/KARAF-3513
> Project: Karaf
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 2.4.2, 3.0.4, 4.0.0.M3
>
>
> when we configure the JMX Connector with SSL enabled, if there's no valid
> keystore available in the first place when start the "Apache Karaf ::
> Management" bundle, that bundle can't pick up any KeystoreInstance available
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";
> xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0";>
> <jaas:keystore name="sample_keystore"
> rank="1"
> path="..."
> keystorePassword="..."
> keyPasswords="..." />
> </blueprint>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a
> KeystoreInstance get published, however, the JMX Connector won't be able to
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf
> :: Management" bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
