On the 08..091 code path, users of the Python API are responsible for forming the SASL response themselves and passing this as an argument to the Client#start method. This approach works only for SASL interactions that do not require a 'secure' step.
The API will be changed so that Client#start accept username/password arguments, and that the client internally selects a suitable SASL mechanism from those offered by the server. SASL mechanisms will be included for:
- SCRAM SHA1/25
- AMQPLAIN/CRAM-MD5-HEX (legacy - to aid interoperability)
The existing API will be maintain through the change. The 0-10 paths will not be impacted by this change.