[jira] [Commented] (KARAF-6888) Sort out JMXMP authentication

["Matt Pavlovich (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264331#comment-17264331 ] 

Matt Pavlovich commented on KARAF-6888:
---------------------------------------

[~jbonofre] have you had a chance to look at this? I think the changes are pretty minor to get jmxmp operational.

> Sort out JMXMP authentication
> -----------------------------
>
>                 Key: KARAF-6888
>                 URL: https://issues.apache.org/jira/browse/KARAF-6888
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf
>    Affects Versions: 4.2.9
>            Reporter: Matt Pavlovich
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>         Attachments: ConnectorServerFactory.java, JMXMPClient.java, JaasAuthenticator.java, PlainSaslServer.java, jre.properties, karaf, org.apache.karaf.management.server-4.2.9.jar
>
>
> Out-of-the-box, karaf's jmxmp support doesn't seem to have a happy path. With the following changes, I'm able to get a list of JMX domains.
> Notes:
> 1. Probably need to support SASL/PLAIN to keep it simple to start, then add TLS
> 2. JDK's don't ship with a SASL/PLAIN Provider anymore, so we need the attached one is adapted from Apache Hive's implementation
> 3. The jmxmp classes and sasl modules need to be added to karaf startup and etc/jre.properties
> 4. Need to solve for a ClassNotFound error for legacy com/sun/jdmk/security/sasl/AuthenticateCallback that is not included in the jmxmp jar in the JaasAuthenticator. 
> 5. -Consider using the javax.management jar instead (as src jars are available for debugging)-
> {noformat}
> <dependency>
>   <groupId>javax.management</groupId>
>   <artifactId>jmx-remote-optional-jmxmp</artifactId>
>   <version>1.0-b06</version>
> </dependency>
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)