sumitgpl / ce-mobile-crm

Automatically exported from code.google.com/p/ce-mobile-crm
0 stars 0 forks source link

Login Failed (fresh install) #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create a user 'testuser'
2. Login to Sugar and set password to 'test1234'
3. Attempt to login via CE Mobile

What is the expected output? What do you see instead?
Expect to see Home Screen, instead get 'login failed' response

What version of the product are you using? On what operating system?
OpenSUSE 11.1 (Kernel 2.6.27.56-0.1-pae) in VMware
PHP 5.2.14, Apache 2.2.10, MySQL 5.0.67
Sugar CE 6.2.0b3 and CE Mobile 0.2.1

Please provide any additional information below.
Fresh install, no other software loaded, always happens on all users.

GET -> 
http://192.168.1.68/sugar/service/v2/rest.php?method=login&input_type=JSON&respo
nse_type=JSON&rest_data=%5B%7B%22password%22%3A%2216d7a4fca7442dda3ad93c9a726597
e4%22%2C%22user_name%22%3A%22testuser%22%7D%2C%22SugarCrm%22%2C%7B%22name%22%3A%
22language%22%2C%22value%22%2C%22en_US%22%7D%5D

RESPONSE -> {"name":"Invalid Login","number":10,"description":"Login attempt 
failed please check the username and password"}

Firebug reports;
input_type  JSON
method  login
response_type   JSON
rest_data   [{"password":"16d7a4fca7442dda3ad93c9a726597e4","user_name":"testuser"
},"SugarCrm",{"name":"language","value","en_US"}]

Original issue reported on code.google.com by dbr...@gmail.com on 17 Apr 2011 at 1:34

GoogleCodeExporter commented 8 years ago

If you use external server for authentication i'm going to post a fix 

could you try with the admin user : must have API rigth
your test user can export ? (no export = no rest or Soap API)

regards

Original comment by jpis...@gmail.com on 19 Apr 2011 at 12:08

GoogleCodeExporter commented 8 years ago
Admin also fails unfortunately.

Also, I'm not familiar with the 'external server for authentication'. This is 
just using a plain old web service login for Sugar; no links to AD/OD/LDAP

Original comment by dbr...@gmail.com on 29 Apr 2011 at 1:54

GoogleCodeExporter commented 8 years ago
I am having the same problem.  Standard install of Version 6.2.0RC1 (Build 6311)

No external server for authentication.  I tried admin user and regular user...

I tried a SOAP based Android App and it was able to login.

Original comment by jason.gr...@gmail.com on 10 May 2011 at 6:03

GoogleCodeExporter commented 8 years ago
I'm going to look in a 6.2 install this week end

Original comment by jpis...@gmail.com on 11 May 2011 at 3:56

GoogleCodeExporter commented 8 years ago
Did you manage to take a look at this?

Original comment by jason.gr...@gmail.com on 16 May 2011 at 4:22

GoogleCodeExporter commented 8 years ago
Is there any workaround for this?  I would like to be able to use your system 
for our sales reps, but I can't get it to work.  Is this project actively being 
worked on?

Original comment by jason.gr...@gmail.com on 26 May 2011 at 4:22

GoogleCodeExporter commented 8 years ago
I have the same problem with 6.2.0RC3 fresh install.
I can't log in with a local user or a LDAP user.
When I look into log file, in the MySQL query, the username is empty...

Original comment by helse...@gmail.com on 30 May 2011 at 2:12

GoogleCodeExporter commented 8 years ago
Should be fixed by r11

Original comment by jmdeleh...@gmail.com on 30 May 2011 at 8:36

GoogleCodeExporter commented 8 years ago
This is not fixed, I replaced the code in Application.js and it still didnt 
work, so I pulled down the latest trunk.  Still no dice!

Original comment by jason.gr...@gmail.com on 30 May 2011 at 9:35

GoogleCodeExporter commented 8 years ago
Actually, I made the same change to ce-mobile-crm-0.0.2.2.js and it solved the 
login issue

Original comment by jason.gr...@gmail.com on 30 May 2011 at 9:43

GoogleCodeExporter commented 8 years ago
It works for me, same version, same bug, resolved by r11.

Did you clear your cache ? 
http://url/to/your/ce-mobile-crm/js/Application.js

Original comment by jmdeleh...@gmail.com on 30 May 2011 at 9:45

GoogleCodeExporter commented 8 years ago
I can confirm that changing the comma to a colon in the .js does fix the issue. 

Thanks

Original comment by dbr...@gmail.com on 3 Jun 2011 at 6:54