[rabbitmq-discuss] Python Client for RabbitMQ/AMQP?

Matthias Radestock matthias at lshift.net
Thu Aug 23 20:14:09 BST 2007


Jeff Rogers wrote:
> I think part of the problem is that the 0.8 spec is confusing on this 
> point.  It says:
> "The contents of this data are defined by the SASL security 
> mechanism.For the PLAIN security mechanism this is defined as a field 
> table holding two fields,LOGIN and PASSWORD."
> However, SASL also defines a mechanism called PLAIN in rfc4616 which is
>    message   = [authzid] UTF8NUL authcid UTF8NUL passwd
> This is what OpenAMQ implements as PLAIN and probably what qpid is doing 
> also (I have a vague recollection that qpid incorrectly leaves off the 
> initial null but that may be bad memory on my part).

So it looks like OpenAMQ, Qpid, and RabbitMQ all use the SASL 
definition, in which case there should be no interop problems in this 
particular area, right?

> So which PLAIN is PLAIN?  Considering that the security is specified in 
> several places as using SASL mechanisms and that language about a 
> LOGIN/PASSWORD field table has been dropped in the 0.9 spec, I think the 
> SASL PLAIN mechanism is the right one to follow.


> Confusion in the spec notwithstanding, my bigger gripe about how 
> rabbitmq is handling it is that the AMQPLAIN method is not advertised at 
> all in the connection.start call, so any use of it is going to be well, 
> gross and brittle as you say.

Given the above, I am tempted to simply remove AMQPLAIN.


More information about the rabbitmq-discuss mailing list