On Seg, 2013-05-20 at 11:13 +0100, Bruno Matos wrote: > On Sex, 2013-05-17 at 15:24 +0100, Gordon Sim wrote: > > > I'm using PLAIN in the domain configuration. I was debugging the > > > creation of the messages in the source broker and notice that the > > > qpid::broker::amqp::SaslClient::getVersion calls the > > > Connection::getVersion method which creates a ProtocolVersion(1,0), > > > leaving the protocol field of ProtocolVersion set to 0. Can this be a > > > problem? > > > > Yes! > > > > > After change that to ProtocolVersion(1,0,3) the destination > > > broker no longer complains about SASL layer. > > > > Great... and does it then work? > > No, the source broker throws an exception on qpid::CyrusSasl::start > +311. In debug mode, I inspected some variables and it seams that > something is missing, I was expecting to see username and password in > conn p.e but it's not set. >
It needs the username and password properties set on domain creation, I thought they were parsed from url. Now, with SASL it doesn't create the queue for the outgoing link. This is because when qpid::broker::amqp::Sasl::canEncode() is called the state is NONE so it doesn't call the Connection::canEncode which would create the queue as when there is no SASL layer and Wrapper::canEncode is called. If at this point I stop the source broker, the destination broker gives 'Connection closed prior to authentication completing' twice, which makes me think that authentication or the handshake were never finished. Could you please help me understand if something is wrong with my configuration or clarify this authentication/handshake process and what may be wrong? Thank you, Regards. -- Bruno Matos --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
