[QPID-5778] CRAM-MD5 mechanism does not work in python-client

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 0.26
• Fix Version/s: Future
• Component/s: Python Client (Wrapped)
• Assignee: Pavel Moravec
• Reporter: Pavel Moravec
• Created: 21/May/14 11:27
• Updated: 23/May/14 10:15
• Resolved: 23/May/14 10:15

Description

CRAM-MD5 mechanism does not work in python client, see e.g.:

$ qpid-stat -q -b guest/guest@localhost:5672 --sasl-mechanism=CRAM-MD5
Failed: ConnectionError - connection-forced: Authentication failed(320)
$ qpid-stat -q -b guest/guest@localhost:5672 --sasl-mechanism=DIGEST-MD5
Queues
queue dur autoDel excl msg msgIn msgOut bytes bytesIn bytesOut cons bind
..
$

The root cause is that Python client sends initial SASL response in ConnectionStartOk AMQP frame even in case it is empty. In such case, it should not set response.