Hi,
Not sure if this is a bug or not, so posting it here rather than in the bug tracker.
Basically, I am unable to add an XMPP identity via the webapp, I continually get the error message: "Unable to connect to the Jabber server. Maybe you entered the wrong password? (Error message: AuthenticationFailure)"
I didn't enter the wrong password, I copy/pasted it from my password manager and the same account/password work fine with Pidgin. The log doesn't show anything of interest that I can see.
Using git annex version 4.20130405 from Debain Unstable. The server is ejabberd running on my VPS with a self signed certificate.
Anyone got any idea what might be going on?
Cheers,
Rob
ejabberdctl register. Filed an upstream bug report against the haskell network-protocol-xmpp library, by email, since there's no upstream BTS:John has gotten back to me with some analysis. The authentication failure is when SCRAM-SHA-1 is used. Ejabberd is rejecting the client's authentication request with a reason of "bad-protocol". It's not clear if ejabberd is broken or if gsasl is generating a bad SCRAM-SHA-1 authentication. We're inclined toward the latter, and will be forwarding this on to ejabberd.
The only way to turn off this authentication in ejabberd is to configure it to store passwords in plain text, or downgrade to a version older than 2.1.9, which first added it. Note that debian stable contains 2.1.5.3, so is not currently affected, for example.
Now that Wheezy is out, Debian Stable appears to be affected by this issue. It has ejabberd v2.1.10 .
The patch on the linked bug report doesn't apply cleanly to v2.1.10. I'll try and look at this again tomorrow.
Ah ha, so it is. I've installed ejabberd from Jessie onto my Wheezy box and now git-annex can authenticate.
Thank you!
I tried logging in to my local 'jabberd' server and got the same response:
AuthenticationError "No supported authentication mechanism"
checking the version gives:
Can I do anything, investigate something?