Project

General

Profile

Bug #563

Beem fails to authenticate using Android 5.0 Lollipop devices

Added by Barbra Conner about 4 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
XMPP
Target version:
-
Start date:
12/19/2014
Due date:
% Done:

0%

Estimated time:
Affected version:
0.1.8
Locale:
Close

Description

Tested on Nexus 4 and Nexus 10 devices.

Error says "Warning: Your settings are set to use a server proxy or a specific server hostname. Unable to authenticate your account. Please verify your credentials"

Is there any further development going on with BEEM as I see it's been more than a year since a new client has been released.

Thanks

History

#1 Updated by Frédéric Barthéléry about 4 years ago

  • Subject changed from BeemFails to authenticate using Android 5.0 Lollipop devices to Beem fails to authenticate using Android 5.0 Lollipop devices
  • Priority changed from High to Normal

This seems to be a configuration issue. Check that your settings are correct specifically for the proxy and specific server configuration.
I have no problem to connect on Lollipop devices.

Regarding the development of Beem, unfortunattely we have less and less time to work on it so the development is stalled for now.

#2 Updated by Barbra Conner almost 4 years ago

Is it possible for Beem to support Old Style SSL connection vs Start TLS?

#3 Updated by Frédéric Barthéléry almost 4 years ago

You can have a look at issue #311 . But we definitelly won't support the old ssl connection method.

#4 Updated by Neil Carter over 3 years ago

Greetings:

This is behaving in the exact same manner on my Motorola Droid Turbo. Since upgrading the OS to Lollipop 5.1, Beem will not authenticate (worked fine with KitKat). It provides the exact same error message with every attempt: "Warning: Your settings are set to use a server proxy or a specific server hostname. Unable to authenticate your account. Please verify your credentials"

There are no proxy servers involved. I've checked the specific server configuration loads of times, everything is very straightfoward, simple, and correct. And my credentials are being entered correctly. Is there a network sniffer for Android that would allow us to monitor the connection to observe the error?

It appears there's an encryption and/or certificate incompatibility involved between the Lollipop OS, Beem, and the Beehive server. It would appear the Lollipop OS has eliminated the ability to use either a certain type of encryption or class of certificate, no longer acceptable from a security standpoint.

Also, if I enable "Enable XMPP debug", where does the debug output go?

Please update and advise.

Thanks!

Neil

#5 Updated by Frédéric Barthéléry over 3 years ago

When you enable "Enable XMPP debug" option, the output goes in the system logcat.
You can get it by running

adb logcat

in a terminal

#6 Updated by Neil Carter over 3 years ago

Actually, regarding the XMPP Debug, I was asking about on my phone...

But what about the rest of the message, my other questions?

Thanks!

Neil

#7 Updated by Frédéric Barthéléry over 3 years ago

You can use a software like wireshark to sniff the communication between your device and the server. But as the communication is probably encrypted you will have to provide the encryption keys of the server. That's why I recommand running adb logcat to get the log on the device instead.

#8 Updated by Neil Carter over 3 years ago

Well, as I don't have a clue how to do 'adb logcat', I'm going to have to pass. I'm a user, not a developer, sorry.

Any other suggestions? We've got thousands of users who can no longer use Beem because of the 5.1 Lollipop update.

Thanks!

Neil

Also available in: Atom PDF