I just tried out beta 2 and have bumped into a problem. I’m using ejabberd 2.0.1 as my server with TLS enabled.
I cannot login with the beta. I opened the debugger to see what the server and client are saying to each other and noticed that the server advertises SASL methods PLAIN and DIGEST-MD5. Spark then requests authentication using CRAM-MD5, which fails with the server saying there is no “common” mechanism to auth with.
How can I fix this?
I started spark with the debugger active and have pasted the resulting raw packet logs below. Hopefully these will help to show what is going wrong:
Raw Sent Packets:
<stream:stream to=“ldmltd.ca” xmlns=“jabber:client” xmlns:stream=“http://etherx.jabber.org/streams” version=“1.0”>
<stream:stream to=“ldmltd.ca” xmlns=“jabber:client” xmlns:stream=“http://etherx.jabber.org/streams” version=“1.0”>
Raw Recieved Packets:
<?xml version='1.0'?>stream:features
DIGEST-MD5PLAIN</stream:features>
stream:featuresDIGEST-MD5PLAIN</stream:features>
I looks to me that Spark is trying to use an auth mechanism that the server is not advertising. Spark 2.5.8 works correctly by using auth method PLAIN, which the server does advertise.
-Greg