[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264331#comment-17264331
]
Matt Pavlovich edited comment on KARAF-6888 at 1/13/21, 6:21 PM:
-
[~jbonofre] have you had a chance to look at this? I think the changes are
pretty minor to get jmxmp operational. It would be great to get this in 4.2.11
and/or 4.3.1. Thanks!
was (Author: mattrpav):
[~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}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215740#comment-17215740
]
Matt Pavlovich edited comment on KARAF-6888 at 10/17/20, 4:45 AM:
--
PR created: https://github.com/apache/karaf/pull/1232
# [x] Built and tested against master
# [x] Tested connect via JMXMP
# [x] Test local jconsole using jmx:rmi (to confirm no regression)
# [x] management module unit tests pass ([INFO] Tests run: 56, Failures: 0,
Errors: 0, Skipped: 0)
# [x] Tested JMXMP with karaf in docker and JMXMP outside of docker
Note: Apologies ahead of time for the ugly refactor of JaasAuthenticator..
quick and dirty to get things working while juggling the Callback array.
was (Author: mattrpav):
PR created: https://github.com/apache/karaf/pull/1232
# [x] Built and tested against master
# [x] Tested connect via JMXMP
# [x] Test local jconsole using jmx:rmi (to confirm no regression)
# [x] management module unit tests pass ([INFO] Tests run: 56, Failures: 0,
Errors: 0, Skipped: 0)
# [x] Tested JMXMP with karaf in docker and JMXMP outside of docker
> 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}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215740#comment-17215740
]
Matt Pavlovich edited comment on KARAF-6888 at 10/17/20, 4:45 AM:
--
PR created: https://github.com/apache/karaf/pull/1232
# [x] Built and tested against master
# [x] Tested connect via JMXMP
# [x] Test local jconsole using jmx:rmi (to confirm no regression)
# [x] management module unit tests pass ([INFO] Tests run: 56, Failures: 0,
Errors: 0, Skipped: 0)
# [x] Tested JMXMP with karaf in docker and JMXMP outside of docker
Note: Apologies ahead of time for the ugly refactor of JaasAuthenticator..
quick and dirty to get things working while juggling the Callback array.
Probably could use a second set of eyes to simplify.
was (Author: mattrpav):
PR created: https://github.com/apache/karaf/pull/1232
# [x] Built and tested against master
# [x] Tested connect via JMXMP
# [x] Test local jconsole using jmx:rmi (to confirm no regression)
# [x] management module unit tests pass ([INFO] Tests run: 56, Failures: 0,
Errors: 0, Skipped: 0)
# [x] Tested JMXMP with karaf in docker and JMXMP outside of docker
Note: Apologies ahead of time for the ugly refactor of JaasAuthenticator..
quick and dirty to get things working while juggling the Callback array.
> 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}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215743#comment-17215743
]
Matt Pavlovich edited comment on KARAF-6888 at 10/17/20, 4:42 AM:
--
-If we want jvisualvm and jconsole to work, we may not be able to specify a
profile.-
Note: jconsole and jvisualvm would need to be updated to support
jmx.remote.profiles.
Output from jvisualvm:
{noformat}
04:35:55.896 WARN [Job_Executor3] Failed to open connection:
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
at
com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.security.AdminServer.connectionOpen(AdminServer.java:123)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.connect(ServerSynchroMessageConnectionImpl.java:98)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:443)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:248)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:99)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
{noformat}
was (Author: mattrpav):
Note: If we want jvisualvm and jconsole to work, we may not be able to specify
a profile.
Output from jvisualvm:
{noformat}
04:35:55.896 WARN [Job_Executor3] Failed to open connection:
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
at
com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.security.AdminServer.connectionOpen(AdminServer.java:123)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.connect(ServerSynchroMessageConnectionImpl.java:98)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:443)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:248)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:99)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
{noformat}
> 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}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215743#comment-17215743
]
Matt Pavlovich edited comment on KARAF-6888 at 10/17/20, 4:42 AM:
--
-If we want jvisualvm and jconsole to work, we may not be able to specify a
profile.-
Note: jconsole and jvisualvm would need to be updated to support
jmx.remote.profiles.
Output from karaf when jvisualvm attempts to connect (jmxmp jar added to
jvisualvm cp)
{noformat}
04:35:55.896 WARN [Job_Executor3] Failed to open connection:
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
at
com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.security.AdminServer.connectionOpen(AdminServer.java:123)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.connect(ServerSynchroMessageConnectionImpl.java:98)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:443)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:248)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:99)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
{noformat}
was (Author: mattrpav):
-If we want jvisualvm and jconsole to work, we may not be able to specify a
profile.-
Note: jconsole and jvisualvm would need to be updated to support
jmx.remote.profiles.
Output from jvisualvm:
{noformat}
04:35:55.896 WARN [Job_Executor3] Failed to open connection:
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
java.io.IOException: java.io.IOException: The client does not require any
profile but the server mandates one
at
com.sun.jmx.remote.opt.security.AdminClient.throwExceptionOnError(AdminClient.java:379)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.security.AdminServer.connectionOpen(AdminServer.java:123)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.generic.ServerSynchroMessageConnectionImpl.connect(ServerSynchroMessageConnectionImpl.java:98)
~[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
javax.management.remote.generic.GenericConnectorServer$ClientCreation.run(GenericConnectorServer.java:443)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at
com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:248)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:99)
[opendmk_jmxremote_optional_jar-1.0-b01-ea.jar:?]
{noformat}
> 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}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215740#comment-17215740
]
Matt Pavlovich edited comment on KARAF-6888 at 10/17/20, 4:20 AM:
--
PR created: https://github.com/apache/karaf/pull/1232
# [x] Built and tested against master
# [x] Tested connect via JMXMP
# [x] Test local jconsole using jmx:rmi (to confirm no regression)
# [x] management module unit tests pass ([INFO] Tests run: 56, Failures: 0,
Errors: 0, Skipped: 0)
# [x] Tested JMXMP with karaf in docker and JMXMP outside of docker
was (Author: mattrpav):
PR created
# [x] Built and tested against master
# [x] Tested connect via JMXMP
# [x] Test local jconsole using jmx:rmi (to confirm no regression)
# [x] management module unit tests pass ([INFO] Tests run: 56, Failures: 0,
Errors: 0, Skipped: 0)
# [x] Tested JMXMP with karaf in docker and JMXMP outside of docker
> 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}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215674#comment-17215674
]
Matt Pavlovich edited comment on KARAF-6888 at 10/16/20, 9:59 PM:
--
Easy happy path testing:
1. Grab apache-karaf-4.2.9-unix.tar.gz
2. Replace these files: bin/karaf, etc/jre.properties,
org.apache.karaf.management.server-4.2.9.jar
3. Start karaf ./bin/karaf debug
4. Run JMXMPClient.java test
Expected output:
{noformat}
Domain[0] = JMImplementation
Domain[1] = java.util.logging
Domain[2] = jdk.management.jfr
Domain[3] = java.lang
Domain[4] = com.sun.management
Domain[5] = connector
Domain[6] = osgi.compendium
Domain[7] = java.nio
Domain[8] = org.apache.karaf
Domain[9] = osgi.core
{noformat}
was (Author: mattrpav):
Easy happy path testing:
1. Grab apache-karaf-4.2.9-unix.tar.gz
2. Replace these files: bin/karaf, etc/jre.properties,
org.apache.karaf.management.server-4.2.9.jar
3. Run JMXMPClient.java test
> Sort out JMXMP authentication
> -
>
> Key: KARAF-6888
> URL: https://issues.apache.org/jira/browse/KARAF-6888
> Project: Karaf
> Issue Type: Improvement
>Affects Versions: 4.2.9
>Reporter: Matt Pavlovich
>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 to
> implement one. 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
> 5. Consider using the javax.management jar instead (as src jars are available
> for debugging)
> {noformat}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KARAF-6888) Sort out JMXMP authentication
[
https://issues.apache.org/jira/browse/KARAF-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215674#comment-17215674
]
Matt Pavlovich edited comment on KARAF-6888 at 10/16/20, 9:56 PM:
--
Easy happy path testing:
1. Grab apache-karaf-4.2.9-unix.tar.gz
2. Replace these files: bin/karaf, etc/jre.properties,
org.apache.karaf.management.server-4.2.9.jar
3. Run JMXMPClient.java test
was (Author: mattrpav):
Easy happy path testing:
1. Grab apache-karaf-4.2.9-unix.tar.gz
2. Replace these files: bin/karaf, etc/jre.properties,
org.apache.karaf.management.server-4.2.9.jar
> Sort out JMXMP authentication
> -
>
> Key: KARAF-6888
> URL: https://issues.apache.org/jira/browse/KARAF-6888
> Project: Karaf
> Issue Type: Improvement
>Affects Versions: 4.2.9
>Reporter: Matt Pavlovich
>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.
> Notes:
> 1. Probably need to support SASL/PLAIN to keep it simple to start
> 2. JDK's don't ship with a SASL/PLAIN Provider anymore
> 3. The jmxmp classes and sasl modules seem to 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
> 5. Consider using the javax.management jar instead (as src jars are available
> for debugging)
> {noformat}
>
> javax.management
> jmx-remote-optional-jmxmp
> 1.0-b06
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
