This should be fixed by the patches I submitted previously, once the remaining ones are applied to the trunk. After repairing the PLAIN authentication, I used CRAM-MD5 several times without any issue.
Also, just a note: removing -Dsecurity=CRAM-MD5 does not make it use PLAIN, it makes the connection to the broker totally unauthenticated. -Dsecurity=PLAIN makes it use PLAIN authentication. -----Original Message----- From: Marnie McCormack (JIRA) [mailto:[EMAIL PROTECTED] Sent: 28 November 2008 11:50 To: [email protected] Subject: [jira] Created: (QPID-1491) Secure Management Console connections do not work[MESSAGE NOT SCANNED] 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.
