In the smack repository rev 10743,
I had to modify the following for SASLMechanism.java under challengeReceived to get it to work with my Ejabberd server. Not sure if it’s the right thing to do though.
String authenticationText = response == null ? "=" : Base64.encodeBytes(response,Base64.DONT_BREAK_LINES);
Hey Jan Vincent,
I guess your fix applies to SASLMechanism#challengeReceived(String). I think that it is a safe fix but I wonder why the server is replying to the client with an empty challenge. SASL may include a sequence of challenge-response until there are no more challenges and you are either approved or not. I’m not an expert on SASL but I think that having an empty challenge is not something clients would expect.