Subject: Digest MD5 failing
Hi Alex,
Been away for a while but when I tried to continue working I get rejected from the amessage.info server as shown by the message flow below. If I force the SaslHandler to send a RequestLoginInfo rather than init one of the sasl.mechanisms the login works fine.
Thanks in advance,
Simon
SEND: <stream:stream to='amessage.info' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' xml:lang='en'>
RECV: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" from="amessage.info" version="1.0" id="1938990772" >
RECV: <stream:features xmlns:stream="http://etherx.jabber.org/streams"><register xmlns="http://jabber.org/features/iq-register" /><auth xmlns="http://jabber.org/features/iq-auth" /><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>NTLM</mechanism><mechanism>LOGIN</mechanism><mechanism>PLAIN</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms></stream:features>
SEND: <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="DIGEST-MD5" />
RECV: <challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">bm9uY2U9IjVoSnE4K3hITC8rNlhxRUpOWERUeHJrOXpEMnNvckVWc2RwYXd4NklrSmM9IixyZWFsbT0iYW1lc3NhZ2UuaW5mbyIscW9wPSJhdXRoLGF1dGgtaW50LGF1dGgtY29uZiIsY2lwaGVyPSJyYzQtNDAscmM0LTU2LHJjNCxkZXMsM2RlcyIsbWF4YnVmPTEwMjQsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge>
SEND: <response xmlns="urn:ietf:params:xml:ns:xmpp-sasl">dXNlcm5hbWU9InNpbW9uaGFtZWxlY2giLHJlYWxtPSJhbWVzc2FnZS5pbmZvIixub25jZT0iNWhKcTgreEhMLys2WHFFSk5YRFR4cms5ekQyc29yRVZzZHBhd3g2SWtKIixjbm9uY2U9IjE3NzU5YzNlMmFmNGE4YTA0NGNjMTk4YmZiNGM4M2RhNmIxMzYzZDExNzA0NjZlNzIwZDU0MjVmMmE4MTgzMTEiLG5jPTAwMDAwMDAxLHFvcD1hdXQsZGlnZXN0LXVyaT0ieG1wcC9hbWVzc2FnZS5pbmZvIixjaGFyc2V0PXV0Zi04LHJlc3BvbnNlPTM0M2E4MWVjMWJmMTFkNjRiNGJiOWRmYWM4MmZlZjc2</response>
RECV: <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized /></failure>
RECV: </stream:stream>
Been away for a while but when I tried to continue working I get rejected from the amessage.info server as shown by the message flow below. If I force the SaslHandler to send a RequestLoginInfo rather than init one of the sasl.mechanisms the login works fine.
Thanks in advance,
Simon
SEND: <stream:stream to='amessage.info' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' xml:lang='en'>
RECV: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" from="amessage.info" version="1.0" id="1938990772" >
RECV: <stream:features xmlns:stream="http://etherx.jabber.org/streams"><register xmlns="http://jabber.org/features/iq-register" /><auth xmlns="http://jabber.org/features/iq-auth" /><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>NTLM</mechanism><mechanism>LOGIN</mechanism><mechanism>PLAIN</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms></stream:features>
SEND: <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="DIGEST-MD5" />
RECV: <challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">bm9uY2U9IjVoSnE4K3hITC8rNlhxRUpOWERUeHJrOXpEMnNvckVWc2RwYXd4NklrSmM9IixyZWFsbT0iYW1lc3NhZ2UuaW5mbyIscW9wPSJhdXRoLGF1dGgtaW50LGF1dGgtY29uZiIsY2lwaGVyPSJyYzQtNDAscmM0LTU2LHJjNCxkZXMsM2RlcyIsbWF4YnVmPTEwMjQsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge>
SEND: <response xmlns="urn:ietf:params:xml:ns:xmpp-sasl">dXNlcm5hbWU9InNpbW9uaGFtZWxlY2giLHJlYWxtPSJhbWVzc2FnZS5pbmZvIixub25jZT0iNWhKcTgreEhMLys2WHFFSk5YRFR4cms5ekQyc29yRVZzZHBhd3g2SWtKIixjbm9uY2U9IjE3NzU5YzNlMmFmNGE4YTA0NGNjMTk4YmZiNGM4M2RhNmIxMzYzZDExNzA0NjZlNzIwZDU0MjVmMmE4MTgzMTEiLG5jPTAwMDAwMDAxLHFvcD1hdXQsZGlnZXN0LXVyaT0ieG1wcC9hbWVzc2FnZS5pbmZvIixjaGFyc2V0PXV0Zi04LHJlc3BvbnNlPTM0M2E4MWVjMWJmMTFkNjRiNGJiOWRmYWM4MmZlZjc2</response>
RECV: <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized /></failure>
RECV: </stream:stream>