Chuck Rolke created QPID-6511:
---------------------------------
Summary: [C++ Broker, clients] AMQP 0-10 windows clients can not
connect to --no-auth broker
Key: QPID-6511
URL: https://issues.apache.org/jira/browse/QPID-6511
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Client
Affects Versions: 0.32
Environment: C++ Broker, windows client (drain or spout)
Reporter: Chuck Rolke
Assignee: Chuck Rolke
Broker
{noformat}
./qpidd --auth no
{noformat}
Windows client
{noformat}
spout -b my-broker:5672 amq.topic
{noformat}
Fails with "Not authenticated!"
The behavior change was in the broker as part of QPID-6325. Arguably the change
is a good thing as it prevents clients connecting to the broker with no name.
However, it makes for a poor out-of-the-box experience with a no-auth broker
rejecting connections with an auth error.
Clients can make a connection by adding:
{noformat}
--connection-options "{username:dummy}"
or
--connection-options "{sasl-mechanisms:ANONYMOUS}"
{noformat}
But the change breaks years of accumulated self tests that work just fine
against older versions of qpidd.
The proposal to fix this is to make the Windows client provide the same
connection defaults as linux cyrus sasl.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
