[jitsi-users] XMPP SASL Digest-MD5 Authentication fails in V2


#1

Hi,
I have currently been using Jitsi V1 authenticating an XMPP account
against an Icewarp server and all has been working ok.
I upgraded to Jitsi V2 (64bit windows) recently and I cannot
successfully authenticate my XMPP account using SASL Digest-MD5. It
repeatedly keeps asking for the password yet i know the password is
correct.
Log shows: SASL authentication DIGEST-MD5 failed:
temporary-auth-failure

If I deactivate MD5 authentication on the server, it successfully
authenticates using SASL PLAIN.

Any ideas?

Log Below:
13:56:02.332 SEVERE: [80]
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVR
ecords().848 Error connecting to mail.mydomain.com./41.78.245.16:5222
for domain:mydomain.com serviceName:mydomain.com
SASL authentication DIGEST-MD5 failed: temporary-auth-failure:
  at
org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthenticati
on.java:337)
  at
org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:219)
  at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1268)
  at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:902)
  at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectUsingSRVRecords(ProtocolProviderServiceJabberImpl.java
:842)
  at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:654)
  at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.reregister(ProtocolProviderServiceJabberImpl.java:529)
  at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.fireRegistrationStateChanged(ProtocolProviderServiceJabberImp
l.java:2001)
  at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
  at
net.java.sip.communicator.util.account.LoginManager$RegisterProvider.ru
n(LoginManager.java:432)


#2

Hi,

can you try adding a custom property to your account configuration by
editing a properties file.
The file is located in your progile folder for Jitsi
https://jitsi.org/faq#jitsi-home with name
sip-communicator.properties.
You must find the entries for your account and enter a property like
this one (acc1310480674993 will be different for your account)
net.java.sip.communicator.impl.protocol.jabber.acc1310480674993.DISABLE_CUSTOM_DIGEST_MD5=true
Does it connect now?

Thanks
damencho

···

On Sat, Apr 13, 2013 at 4:50 PM, <jrndegwa@hotmail.com> wrote:

Hi,
I have currently been using Jitsi V1 authenticating an XMPP account
against an Icewarp server and all has been working ok.
I upgraded to Jitsi V2 (64bit windows) recently and I cannot
successfully authenticate my XMPP account using SASL Digest-MD5. It
repeatedly keeps asking for the password yet i know the password is
correct.
Log shows: SASL authentication DIGEST-MD5 failed:
temporary-auth-failure

If I deactivate MD5 authentication on the server, it successfully
authenticates using SASL PLAIN.

Any ideas?

Log Below:
13:56:02.332 SEVERE: [80]
impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectUsingSRVR
ecords().848 Error connecting to mail.mydomain.com./41.78.245.16:5222
for domain:mydomain.com serviceName:mydomain.com
SASL authentication DIGEST-MD5 failed: temporary-auth-failure:
        at
org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthenticati
on.java:337)
        at
org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:219)
        at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1268)
        at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:902)
        at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectUsingSRVRecords(ProtocolProviderServiceJabberImpl.java
:842)
        at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:654)
        at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.reregister(ProtocolProviderServiceJabberImpl.java:529)
        at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.fireRegistrationStateChanged(ProtocolProviderServiceJabberImp
l.java:2001)
        at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJ
abberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
        at
net.java.sip.communicator.util.account.LoginManager$RegisterProvider.ru
n(LoginManager.java:432)


#3

Hi Damencho,
Thanks for the response.

Yes adding that custom property substituting with my account details
allows it connect successfully. Cheers for that :slight_smile:

Is there a bug in the smack version used in Jitsi V2 when it comes to
MD5? I had seen some old posts online pointing to issues with SASL.

Regards,
John


#4

Hi Damencho,
Thanks for the response.

Yes adding that custom property substituting with my account details
allows it connect successfully. Cheers for that :slight_smile:

Is there a bug in the smack version used in Jitsi V2 when it comes to
MD5? I had seen some old posts online pointing to issues with SASL.

Regards,
John


#5

Hi Damencho,
Thanks for the response.

Yes adding that custom property substituting with my account details
allows it connect successfully. Cheers for that :slight_smile:

Is there a bug in the smack version used in Jitsi V2 when it comes to
MD5? I had seen some old posts online pointing to smack issues with
SASL.

Regards,
John
.


#6

Hi Damencho,
Thanks for the response.

Yes adding that custom property substituting with my account details
allows it connect successfully. Cheers for that :slight_smile:
net.java.sip.communicator.impl.protocol.jabber.acc1310480674993.DISABLE
_CUSTOM_DIGEST_MD5=true

Is there a bug in the smack version used in Jitsi V2 as compared to V1
when it comes to
MD5? I had seen some old posts elsewhere online pointing to issues with
smack SASL authentication.

Regards,
John