[
https://issues.apache.org/jira/browse/QPID-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971816#action_12971816
]
Steve Huston commented on QPID-2979:
------------------------------------
Comment from this thread in email before it got to JIRA, from Gordon Sim:
Ok, as you can see the windows broker behaves slightly differently with
--auth no, and only offers ANONYMOUS.
Unfortunately at present there is no implementation of that mechanism
for java (either in the SunSASL provider or explicitly provided by
Qpid). It would not be difficult to add I imagine.
Perhaps the behaviour of the windows broker in this regard has changed
in 0.8, intentionally or otherwise(?). However I can't see any obvious
change.
It would be an easy fix on the broker side (the handling of PLAIN is
still there for the auth=no case, just need to advertise the mech).
==============================================================
Thus, there may be two issues here that are intersecting:
1. The Java client doesn't do ANONYMOUS
2. The C++ Windows broker doesn't offer PLAIN when --auth no is set (although
from the jira report, it once did)
> The following SASL mechanisms [PLAIN] specified by the client are not
> supported by the broker
> ---------------------------------------------------------------------------------------------
>
> Key: QPID-2979
> URL: https://issues.apache.org/jira/browse/QPID-2979
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.8
> Environment: Windows XP
> Reporter: Ibisek
> Fix For: 0.6
>
>
> An exception is thrown when connecting from a Java client (v 0.8) to qpidd (v
> 0.8) run with "--auth no".
> javax.jms.JMSException: Error creating connection: The following SASL
> mechanisms [PLAIN] specified by the client are not supported by the broker
> at
> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
> Used JNDI/JMS configuration:
> java.naming.factory.initial =
> org.apache.qpid.jndi.PropertiesFileInitialContextFactory
> connectionfactory.qpidConnectionfactory =
> amqp://guest:gu...@clientid/abcd?brokerlist='tcp://localhost:5672'
> destination.mainSend = direct://amq.direct//step.01
> It worked just fine in 0.6 but no success now in 0.8.
> The broker is from Contributed C++ Packages -> Windows Installer
> (http://www.riverace.com/qpid/qpidc-0.8-x86.msi)
> Logs from qpidd:
> C:Program Filesapache-qpidc-0.8bin>qpidd --auth no --log-enable info+
> --log-enable trace+:amqp_0_10
> 2010-12-15 11:42:48 info Management enabled
> 2010-12-15 11:42:48 notice SASL disabled: No Authentication Performed
> 2010-12-15 11:42:48 info Policy file not specified. ACL Disabled, no ACL
> checking being done!
> 2010-12-15 11:42:48 error Failed to initialise SSL listener: The credentials
> supplied to the package were not recognized (........cpps
> rcqpidbrokerwindowsSslProtocolFactory.cpp:177)
> 2010-12-15 11:42:48 notice Listening on TCP port 5672
> 5672
> 2010-12-15 11:42:48 notice Broker running
> 2010-12-15 11:42:53 trace SENT 127.0.0.1:1786 INIT(0-10)
> 2010-12-15 11:42:53 trace SENT [127.0.0.1:1786]: Frame[BEbe; channel=0;
> {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
> tr16(96790865-dc5c-427a-affe-70d021653737)};
> mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
> Run it with the -t option:
> 2010-12-15 11:45:56 trace SEND raiseEvent (v1)
> class=org.apache.qpid.broker.clientDisconnect
> 2010-12-15 11:46:01 debug RECV [127.0.0.1:1794] INIT(0-10)
> 2010-12-15 11:46:01 trace SENT 127.0.0.1:1794 INIT(0-10)
> 2010-12-15 11:46:01 trace SENT [127.0.0.1:1794]: Frame[BEbe; channel=0;
> {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
> tr16(96790865-dc5c-427a-affe-70d021653737)};
> mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
> 2010-12-15 11:46:01 debug DISCONNECTED [127.0.0.1:1794]
> 2010-12-15 11:46:01 trace SEND raiseEvent (v1)
> class=org.apache.qpid.broker.clientDisconnect
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
