Oh, I see. I thought that SASL mechanisms influence just the authentication
phase. Thank you very much for clarification. So there is probably something
wrong with my proton client because the problem occurs with the standard
example as well:

$ PN_TRACE_FRM=1 python
/usr/local/share/proton-0.16.0/examples/python/simple_send.py -a
myUser:myPassword@localhost/amq.fanout -m 1
[0x9839880]:  -> SASL
[0x9839880]:  <- SASL
[0x9839880]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=:"DIGEST-MD5"]
[0x9839880]:0 -> @sasl-init(65) [mechanism=:"DIGEST-MD5"]
[0x9839880]:0 <- @sasl-challenge(66)
[challenge=b"nonce="Cq5chKnatfwEV28lxxdQw5bD3vxywxUSRnTJ2tLD5ro=",realm="QPID",qop="auth,auth-int,auth-conf",cipher="rc4-40,rc4-56,rc4,des,3des",maxbuf=65535,charset=utf-8,algorithm=md5-sess"]
[0x9839880]:0 -> @sasl-response(67)
[response=b"username="myUser",realm="QPID",nonce="Cq5chKnatfwEV28lxxdQw5bD3vxywxUSRnTJ2tLD5ro=",cnonce="MZV40TRDnt4gzIFENyrdc40fgSNpWXY5jv3v4bOC2vE=",nc=00000001,qop=auth-conf,cipher=rc4,maxbuf=32768,digest-uri="amqp/localhost",response=2dfde3790620d0aede423b17f8edb4a1"]
[0x9839880]:0 <- @sasl-challenge(66)
[challenge=b"rspauth=cf464b4a887edbb1392fc95e5f9f972c"]
[0x9839880]:0 -> @sasl-response(67) [response=b""]
[0x9839880]:0 <- @sasl-outcome(68) [code=0]
[0x9839880]:  <- EOS
[0x9839880]:  -> EOS
ERROR:root:amqp:connection:framing-error: AMQP header mismatch: Unknown
protocol
['\x00\x00\x00\x18S\xd8\xf6\xd6q\xde\xbd\xd3\x06\xb8X\xb53g\xd0\xba\xe4\x8b\x00\x01\x00\x00\x00\x00']

Is it possible that I inadvertently compiled my proton binaries without
support for DIGEST-MD5? Just to explain what I did - I first compiled and
installed the proton 0.16 binaries and then used pip to download and install
the python-qpid-proton 0.16 package.



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-C-1-36-issues-an-invalid-AMQP-1-0-frame-after-successful-DIGEST-MD5-authentication-tp7657354p7657361.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to