Andreas, are you planning to fix the bug in the future version?
It is fixed now:
http://www.swiftmq.com/products/releasenotes/v942/index.html
--
Andreas Mueller
IIT Software GmbH, Bremen/Germany
http://www.swiftmq.com
IIT Software GmbH
Fahrenheitstr. 13, D28359 Bremen, Germany
Tel: +49
Hi,
Messenger will simply use anonymous if you don't specify a username and
password, e.g. amqp://broker/node will result in the client forcing
ANONYMOUS. If you do specify a username and password, e.g.
amqp://user:pass@broker/node, then messenger will force PLAIN. There is no
way to disable SASL
Disabling SASL should be an option in proton to connect to simple services that
do not provide SASL or just to skip this additional step if SASL is not
requires.
The other problem was already reported from Sergey.
I receive a SASL protocol header and a SASL Init message with mechanism PLAIN
Am 14.01.2014 um 16:00 schrieb Rafael Schloming r...@alum.mit.edu:
The SASL header looks
to start where you see the sequence ...AMQP\x03\x01 This either means
that proton's internal buffers are getting messed up somehow, or there
actually is garbage on the wire.
Just checked with
Andreas, are you planning to fix the bug in the future version?
Thanks,
Sergejs.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/SASL-proton-c-questions-tp7602690p7602711.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
Yes, very soon.
Andreas
Am 14.01.2014 um 18:34 schrieb serega sergejs.melde...@sap.com:
Andreas, are you planning to fix the bug in the future version?
Thanks,
Sergejs.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/SASL-proton-c-questions
