You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robert Gemmell (JIRA)" <qp...@incubator.apache.org> on 2008/12/12 18:10:44 UTC
[jira] Commented: (QPID-1491) Secure Management Console connections
do not work
[ https://issues.apache.org/jira/browse/QPID-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656068#action_12656068 ]
Robert Gemmell commented on QPID-1491:
--------------------------------------
This has been resolved through QPID-794 and QPID-1481 , CRAM-MD5 JMXMP connections are now possible.
> Secure Management Console connections do not work
> -------------------------------------------------
>
> Key: QPID-1491
> URL: https://issues.apache.org/jira/browse/QPID-1491
> Project: Qpid
> Issue Type: Bug
> Components: Java Management : JMX Console
> Affects Versions: M3
> Reporter: Marnie McCormack
>
> Summary:
> The current build of the management console is unable to connect to the broker using the CRAM-MD5 JMX SASL.
> It is potentially a classpath problem with a newer JDK version than was originally tested as the console reports it cannot load a class from the JMXRemote jar.
> Current work around is to use the default PLAIN authentication
> Have to edit qpidmc.bat and remove -Dsecurity=CRAM-MD5
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.