Bug 804616

*** Bug 823802 has been marked as a duplicate of this bug. ***

The work here is to establish that it is working on 0.22/2.4.

Works on 0.22

  2013-04-25 11:28:16 [Security] info qpid/broker/SaslAuthenticator.cpp:415: SASL: Starting authentication with mechanism: CRAM-MD5

...and perftest connects & runs to completion.

nihil obstat - imprimatur.

Sorry to say, I need to return to ASSIGNED as this defect looks in the same state as in time of defect filling:
...
dur:16, tst_cnt:15, err_cnt:0, ecodes:(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)
================== tstbatch localhost guest guest CRAM-MD5 True ==================
1579    24.2455 751.736 0.734117
Failed: ConnectionError - connection-forced: Authentication failed(320)
Failed: ConnectionError: connection-forced: Authentication failed(320)
Failed: ConnectionFailed - (None, 'connection-forced: Authentication failed')
Message(properties={'spout-id': '8e52ebba-cb30-40ac-bcc3-0b749f11ed05:0'}, content_type='t
ext/plain')
===---=== SUMMARY ===---===
dur:17, tst_cnt:20, err_cnt:3, ecodes:(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(1)(1)(1)(0)
...

Which means qpid-perftest and python spout are and were functional, however qpid-tools (here qpid-stat and qpid-config) are still failing.


-> ASSIGNED

Component corrected to qpid-tools + summary tuned.

Mick, please look at this one again.

(In reply to Frantisek Reznicek from comment #6)
> Sorry to say, I need to return to ASSIGNED as this defect looks in the same
> state as in time of defect filling:
> ...
> dur:16, tst_cnt:15, err_cnt:0,
> ecodes:(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)
> ================== tstbatch localhost guest guest CRAM-MD5 True
> ==================
> 1579    24.2455 751.736 0.734117
> Failed: ConnectionError - connection-forced: Authentication failed(320)
> Failed: ConnectionError: connection-forced: Authentication failed(320)
> Failed: ConnectionFailed - (None, 'connection-forced: Authentication failed')
> Message(properties={'spout-id': '8e52ebba-cb30-40ac-bcc3-0b749f11ed05:0'},
> content_type='t
> ext/plain')
> ===---=== SUMMARY ===---===
> dur:17, tst_cnt:20, err_cnt:3,
> ecodes:(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(0)(1)(1)(1)(0)
> ...
> 
> Which means qpid-perftest and python spout are and were functional, however
> qpid-tools (here qpid-stat and qpid-config) are still failing.
> 
> 
> -> ASSIGNED

Yes, sorry -- I tested with wrong tools before.

I see the problem now, with latest packages  (see list below ) 
on both qpid-tool and qpid-config 

Both of them succeed when using DIGEST-MD5, and both fail when using CRAM-MD5

This was on RHEL 6.4

packages
{
cyrus-sasl-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-gssapi-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-md5-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-plain-2.1.23-13.el6_3.1.x86_64
python-qpid-0.22-4.el6.noarch
python-qpid-qmf-0.22-7.el6.x86_64
python-saslwrapper-0.22-3.el6.x86_64
qpid-cpp-client-0.22-8.el6.x86_64
qpid-cpp-client-devel-0.22-8.el6.x86_64
qpid-cpp-client-devel-docs-0.22-8.el6.noarch
qpid-cpp-client-rdma-0.22-8.el6.x86_64
qpid-cpp-client-ssl-0.22-8.el6.x86_64
qpid-cpp-debuginfo-0.22-8.el6.x86_64
qpid-cpp-server-0.22-8.el6.x86_64
qpid-cpp-server-devel-0.22-8.el6.x86_64
qpid-cpp-server-ha-0.22-8.el6.x86_64
qpid-cpp-server-rdma-0.22-8.el6.x86_64
qpid-cpp-server-ssl-0.22-8.el6.x86_64
qpid-cpp-server-store-0.22-8.el6.x86_64
qpid-cpp-server-xml-0.22-8.el6.x86_64
qpid-cpp-tar-0.22-8.el6.noarch
qpid-java-client-0.22-5.el6.noarch
qpid-java-common-0.22-5.el6.noarch
qpid-java-example-0.22-5.el6.noarch
qpid-proton-c-0.4-2.2.el6.x86_64
qpid-proton-c-devel-0.4-2.2.el6.x86_64
qpid-proton-debuginfo-0.4-2.2.el6.x86_64
qpid-qmf-0.22-7.el6.x86_64
qpid-qmf-debuginfo-0.22-7.el6.x86_64
qpid-qmf-devel-0.22-7.el6.x86_64
qpid-snmpd-1.0.0-12.el6.x86_64
qpid-snmpd-debuginfo-1.0.0-12.el6.x86_64
qpid-tests-0.22-4.el6.noarch
qpid-tools-0.22-3.el6.noarch
saslwrapper-0.22-3.el6.x86_64
saslwrapper-devel-0.22-3.el6.x86_64

}

Whole python client does not support CRAM-MD5 authentication mechanism; try to run the attached client example to reproduce the issue, please.

Created attachment 823997 [details]
Python client CRAM-MD5 issue reproducer

Try to run the qmf2_qpid_ctrl.py client, please:

# ./qmf2_qpid_ctrl.py  --broker guest/guest@<hostname>:5672 --sasl-mechanisms CRAM-MD5 query type=queue name=q

The example works with PLAIN, ANONYMOUS and DIGEST-MD5 mechanisms well, but does not work with CRAM-MD5 mechanism.