Bug 338891

Summary:	SASL Autenthication error while connecting to Jabber-Server
Product:	[Unmaintained] kopete	Reporter:	kde
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED FIXED
Severity:	major	CC:	martinralbrecht, pali.rohar
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description kde 2014-09-08 02:53:51 UTC

When adding an existing Jabber account to Kopete I get following error on connect:
"Kopete: Connection problem with Jabber server swissjabber.ch
There was an error authenticating with the server: Bad SASL authentication protocol. Offered mechanisms: SCRAM-SHA-1, PLAIN, DIGEST-MD5"

However when I register a new account on the same server this account works without problems despite the settings are identical from what I can see in the GUI

Settings are: 
use old ssl-encryption: no
allow plain-text password authentication: yes
override default server information: no

Kopete version is 1.6.60 on Kubuntu 14.04

I have the same problem with another account on a different jabber-server  (jabber.at), but connecting with those accounts with same credentials work on different clients (jitsi, telepathy) so the problem must be somewhere within Kopete and since an ICQ account works without problems I guess it is related only to Jabber.
I have tested it on two different Kubuntu 14.04 installations with same result.

Reproducible: Always

Steps to Reproduce:
1. Add an existing Jabber account with default settings as stated above
2. try to connect
3.

Actual Results:  
error message as shown above and failure of connection

Expected Results:  
succesful connection

swissjabber.ch runs Prosody 0.9.4 and jabber.at runs ejabberd 14.07 as server software according to xmpp.net.

Comment 1 Pali Rohár 2014-09-17 19:30:05 UTC

Can you provide output from XML console (rigth click on jabber account)?

Comment 2 kde 2014-09-18 08:20:17 UTC

(In reply to Pali Rohár from comment #1)
> Can you provide output from XML console (rigth click on jabber account)?

here is the output of xml console

<?xml version="1.0"?>

<stream:stream xmlns:stream="http://etherx.jabber.org/streams" version="1.0" xmlns="jabber:client" to="swissjabber.ch">

<?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' version='1.0' from='swissjabber.ch' id='ff41a3d0-6a3c-46e7-a22c-eb6140fbca5c' xml:lang='en' xmlns='jabber:client'>

<stream:features>
<register xmlns="http://jabber.org/features/iq-register"/>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>SCRAM-SHA-1</mechanism>
</mechanisms>
<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
</stream:features>

<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

<proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

<?xml version="1.0"?>

<stream:stream xmlns:stream="http://etherx.jabber.org/streams" version="1.0" xmlns="jabber:client" to="swissjabber.ch">

<?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' version='1.0' from='swissjabber.ch' id='142519e2-6d30-4258-ac2d-aa81c1b07d04' xml:lang='en' xmlns='jabber:client'>

<stream:features>
<register xmlns="http://jabber.org/features/iq-register"/>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>SCRAM-SHA-1</mechanism>
<mechanism>PLAIN</mechanism>
</mechanisms>
<auth xmlns="http://jabber.org/features/iq-auth"/>
</stream:features>

<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="SCRAM-SHA-1">biwsbj1waGlsaXBwLndhbGxlcnQscj1WaWY0V0tQZHZTaXhRdmNtcm50cGRnODJ0ckR4SExlR2s0d2V2S2hteUFBPQ==</auth>

<challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">cj1WaWY0V0tQZHZTaXhRdmNtcm50cGRnODJ0ckR4SExlR2s0d2V2S2hteUFBPTI0MjIxNzNmLThiZTQtNDBmMi05NTU3LWJjNDkwNzFlMjAxNCxzPVl6Um1aVEJsWTJFdFlUWmlPUzAwTjJRekxUazRZekl0TURWaE1ESXpNakV5TlRVdyxpPTQwOTY=</challenge>

Comment 3 Pali Rohár 2015-03-15 13:34:46 UTC

I updated libiris library in kopete git. Libiris contains some fixes to SCRAM-SHA-1 authentication, so please check if kopete from git fixes your problem.

Comment 4 Pali Rohár 2016-10-23 15:09:11 UTC

SCRAM-SHA-1 is already supported, closing.