Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.24
-
None
Description
There is a bug in the SASL client logic in qpidd such that if it gets a successful SASL-OUTCOME before it has sent SASL-INIT, then it immediately moves on to the AMQP header rather than sending the necessary SASL-INIT anyway.
This means that connecting to e.g. dispatch-router or the recv example with proton messenger doesn't work.