MotoDroid -> SugarCRM Community Edition

[GoogleCodeExporter]

What steps will reproduce the problem?
1. enter soap URL and credentials
2. attempt to login
3.

What is the expected output? What do you see instead?
Login failed, check the network

What version of the product are you using? On what operating system?
Current, Motorola/Verizon Droid, Android OS 2.0

Please provide any additional information below.
Sugar Version 5.2.0k (Build 5837), the soap.php file is in the root dir of
the install so changed the URL accordingly. Webserver log files simply show:
10.127.1.146 - - [12/Nov/2009:13:42:35 -0500] "POST /soap.php HTTP/1.1" 200
842 "-" "kSOAP/2.0-Excilys"

Our install of Sugar is configured to do AD authentication too BTW.

Thanks!

Original issue reported on code.google.com by wdin...@gmail.com on 12 Nov 2009 at 6:43

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I got this error until I changed the Sugar URL to 
http://my.sugarserver.com/soap.php.  
I am using the 5.5 beta. 

It will then just tell me that my login is incorrect.  It does this with the 
demo url 
listed in the Manual for Developers, with user will and password will.

I am guessing SugaDroid is not working with the MotoDroid yet?

Original comment by njo...@gmail.com on 5 Dec 2009 at 1:50

[GoogleCodeExporter]

ServiceClientKsoap2Impl( 8201): Calling action [login] on service [http://path 
to my 
crm/soap.php]
SingleClientConnManager( 8201): Invalid use of SingleClientConnManager: 
connection 
still allocated.
SingleClientConnManager( 8201): Make sure to release the connection before 
allocating 
another one.
SugarServiceClientKsoap2Impl( 8201): Invalid Login (10)
SugarServiceClientKsoap2Impl( 8201): Login attempt failed please check the 
username 
and password
LoginInTask( 8201): 
com.excilys.sugadroid.services.exceptions.LoginFailedException: 
Invalid Login (10)
LoginInTask( 8201):   at 
com.excilys.sugadroid.services.impl.ksoap2.LoginServicesKsoap2Impl.login(LoginSe
rvice
sKsoap2Impl.java:70)

Original comment by themee...@gmail.com on 12 Jan 2010 at 4:09

[GoogleCodeExporter]

I am getting the same connection failed error "please check username and 
password". I
even tried creating a new user.

Original comment by ryanpcha...@gmail.com on 2 Feb 2010 at 5:04

[GoogleCodeExporter]

i could not connect to the server and then changed it as mentioned above to the 
/soap.php and then i received 
"check username and password" as well.

is this project still ongoing? i would gladly donate to have a nice Sugar app 
for my Android phones.

thanks

Original comment by seancmas...@gmail.com on 22 Feb 2010 at 4:20

[GoogleCodeExporter]

I've been getting the same errors.  One thing not mentioned yet, when I'm on my 
local
wi-fi, it connects and works fine, but no connection when going through 
Verizons network.

Original comment by danwel...@gmail.com on 29 Mar 2010 at 6:10

[GoogleCodeExporter]

I pulled down the source and discovered, in the documentation, a solution for 
this
problem.  First, I had to make sure that, as above, /soap.php was in the root 
of my
url.  Then (in ver 5.xx), go to "admin>system settings>advanced" and disable
"Validate user IP address".  Once this was turned off, everything worked 
perfectly.

Original comment by danwel...@gmail.com on 29 Mar 2010 at 7:21

[GoogleCodeExporter]

I've used both a WiFi connection and the wireless 3G connection still gives me 
a 
'check username or password' error.  I've added the 'soap.php' fix so that I 
actually 
get to this point. I've tried the "Validate user IP address" fix, but I still 
get the 
same error.

And I'm with seancmasters - I'll happily pony-up some cash to a developer who 
wants 
to handle the project...

I'm using Motorola Droid, 2.1update1.

Original comment by andrew.s...@gmail.com on 4 Apr 2010 at 4:02

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm using a HTC Magic with android 1.6
Same problem. "Login failed,...check your........"
The 'Validate user IP address' option is disabled.
App connects when using url instead of an hostname. App loading and I'm in.

The app tels me that I'm logged In. But that's all,...nothing functions. After 
a few 
minutes the app disconnects.

Original comment by grimb...@gmail.com on 20 Apr 2010 at 7:27

[GoogleCodeExporter]

I just tested the application with SugarCRM CE 5.5 and could not login eighther.
Disabling the IP.check did not help.
So I set the Sugar-Log to debug and inspected the calls being made;
Result: SugaDroid is the sending the User's Password in plaintext and not 
encrypted;
The SugarCRM-SOAP-Connnector then does something like:

SELECT * from users where user_name='johndoe' AND 
user_hash='johndoespasswordclear' 
AND ...

which will not work as the field user_hash does not contain 
"johndoespasswordclear" 
but rather some hashed pw-string.

So I went ahead and looked up the hashed string in sugarCRMs mysql-db, entered 
that 
one as password, and VOILA! Loging worked fine.

regards georg

PS: the hashed string is pretty long and cumbersum to enter on the droids 
virtual 
keyboard, so you may do the same as I did: send yourself a SMS containing the 
string 
and then copy+paste form SMS to the login dialog.

PPS: accounts and contacts did work somehow; Appointments returned only "Action 
failed";

Original comment by kuehnber...@gmail.com on 2 May 2010 at 6:17

[GoogleCodeExporter]

I'm unable to loging in. I still get the "Login failed. Check the network" 
message.
I have try to enter the hashed password on the SugaDroid and nothing.

What can I do to login in with no errors?

Original comment by jvrsanj...@gmail.com on 20 May 2010 at 3:28

[GoogleCodeExporter]

I am getting the "Login failed. Check the network" message as well... is this 
project dead?

Original comment by brhellman@gmail.com on 26 Jul 2010 at 2:49

[GoogleCodeExporter]

Can the author comment on whether or not this project is dead? 

Original comment by brhellman@gmail.com on 16 Aug 2010 at 11:19

[GoogleCodeExporter]

That looks like an issue with the http connection. More than one connection at 
the same time. It is know that this causes on some devices (=Android builds) 
problems that use a different Apache Http Library. 

Original comment by friedger@gmail.com on 26 Oct 2010 at 7:54