anupmishra20 / opendatakit

Automatically exported from code.google.com/p/opendatakit
0 stars 0 forks source link

HTTP Status 401 - Authentication Failed: Log in failed - identity could not be verified #741

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
i install ODK Aggregate v1.2.0 windows-installer on my PC 
bellow is the enviroment that i use:

OS: windows 7
Mysql version: mysql 5.5
tomcat version: tomcat 6.0

Every thing is ok with the installation and i can access to the login page of 
ODKAggregate (http://localhost:8080/ODKAggregate)

But when i try to log in with Google i get the following error message :
HTTP Status 401 - Authentication Failed: Log in failed - identity could not be 
verified

type Status report
message Authentication Failed: Log in failed - identity could not be verified
description This request requires HTTP authentication.

Can i have someone to help me please?

Original issue reported on code.google.com by rohlinb2...@gmail.com on 8 Jan 2013 at 9:03

GoogleCodeExporter commented 9 years ago

Original comment by wbrune...@gmail.com on 14 Jan 2013 at 4:29

GoogleCodeExporter commented 9 years ago
It is likely that you are logged into google with an account that is different 
from the Google account that you specified during the installer.  The first 
time you log in, you must log in through whatever that account was. 

To see what you specified in the installer, you can look at the catalina log in 
your Tomcat logs directory (e.g., C:\Program Files\Apache Software 
Foundation\Tomcat 6.0\logs\catalina.2013-01-10.log ). search for a line 
containing 'superUserEmail'. The e-mail address specified is the one you must 
log in as. From your browser, first go to Google and log into that e-mail 
address (and out of any other account you might have logged in as). Then return 
to the Aggregate page and log in. It should work.

Original comment by mitchellsundt@gmail.com on 14 Jan 2013 at 5:44

GoogleCodeExporter commented 9 years ago
Thank you for answering me.

I already check the superUserEmail that i see in the log of tomcat and log in 
with Google first. when i go to the Aggragate page login  i get the same error.

I reinstall the ODKAggregate and specify a new email adress i get the same 
error.

Thank you.

Original comment by maxy.jea...@gmail.com on 15 Jan 2013 at 5:04

GoogleCodeExporter commented 9 years ago
Attach the Catalina log to this ticket, or send it to me directly ( 
mitchellsundt@gmail.com ) and I'll take a look. Also, scan through it searching 
for errors. It may be that you forgot to install the MySQL Connector/J ???

Original comment by mitchellsundt@gmail.com on 15 Jan 2013 at 6:37

GoogleCodeExporter commented 9 years ago
Hi, 

Find attached the catalina logs. I have installed the MySQL Connector/J. 

Original comment by maxy.jea...@gmail.com on 16 Jan 2013 at 7:49

Attachments:

GoogleCodeExporter commented 9 years ago
Looks like the time of day on your server is wrong. Check the timezone setting.
Also, after changing the time, be sure to stop and restart the Tomcat service.
You may also need to reboot the system (I am surprised by that, but one user 
reported needing to do that to fix the issue; if you find a timezone error and 
correct it and it doesn't work after stopping and starting tomcat, then try the 
reboot too.).

WARNING: Nonce is too old: 2013-01-16T19:46:23ZVOusMVd0WaLJQQ
Jan 16, 2013 2:47:13 PM org.openid4java.consumer.ConsumerManagerImpl verify
SEVERE: Nonce verification failed.

Original comment by mitchellsundt@gmail.com on 16 Jan 2013 at 7:59

GoogleCodeExporter commented 9 years ago
Actually my Timezone is (UTC-06:00) Central Time (US & Canada). I dont 
understand why i get this time  2013-01-16T19:46:23 in the logs. 

Original comment by maxy.jea...@gmail.com on 16 Jan 2013 at 10:03

GoogleCodeExporter commented 9 years ago
You should also check the timezone on the device attempting to connect to the 
server. If either is in disagreement as to the actual GMT time, then the login 
will fail.

I don't know how this can happen. There might be a BIOS clock that is accessed 
in some way that is not set properly?

If you figure out what is wrong, please let me know so I can add it to the 
documentation.  This is a rare but frustrating problem.

Original comment by mitchellsundt@gmail.com on 16 Jan 2013 at 10:07

GoogleCodeExporter commented 9 years ago
I try to connect from the server side. I did not use any other device to access 
the server. 

Original comment by maxy.jea...@gmail.com on 16 Jan 2013 at 10:13

GoogleCodeExporter commented 9 years ago
Hi. I am experiencing exactly the same problem. Only difference is my 
superUserEmail entry doesn't even show up in the logs. 

LOg file attached.

Thanks.

Lawrence

Original comment by qhol...@gmail.com on 16 Aug 2013 at 2:59

Attachments:

GoogleCodeExporter commented 9 years ago
gholloi -- in the future, please create a new issue rather than adding a 
comment to an existing one. In this case, your problem is very different from 
the reported issue.

The log does contain this error:

java.net.UnknownHostException: ip-172-31-39-23.localdomain: 
ip-172-31-39-23.localdomain: Name or service not known

Wherever you entered that string (ip-172-31-39-23.localdomain), it was 
incorrect. Or, if it is correct, the DNS name server (gateway) that you have 
configured for your system does not have that name recorded, or cannot obtain 
the physical IP address for that name from any gateway that the gateway itself 
has access to.

Please read 

http://opendatakit.org/use/aggregate/tomcat-install/#Configure_for_Network_Acces
s

And re-run your ODK Aggregate installer, specifying an appropriate hostname for 
your server. 

Original comment by mitchellsundt@gmail.com on 16 Aug 2013 at 4:50

GoogleCodeExporter commented 9 years ago
In particular...

The name 'ip-172-31-39-23.localdomain' is likely an internal name used within 
the web hosting company to refer to this machine.

During the running of the ODK Aggregate installer, you need to specify the DNS 
name or static ip (public load balancer IP address) that you intend users to 
use when accessing your host. 

Original comment by mitchellsundt@gmail.com on 16 Aug 2013 at 6:23

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Closing this issue. 

Original comment by mitchellsundt@gmail.com on 14 Mar 2014 at 1:01

GoogleCodeExporter commented 9 years ago
Hi  I try to sign in to google account but I couldn't,could you tell me what I 
have to do,thanks

Original comment by Eriyanto...@gmail.com on 15 May 2014 at 6:56

GoogleCodeExporter commented 9 years ago
This ticket is closed. Use the opendatakit@ list first, and only create an 
issue if there is a confirmed bug.  Issues are not an effective way to get 
timely assistance.

Original comment by mitchellsundt@gmail.com on 15 May 2014 at 6:18

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
:) :(

Original comment by elabela...@gmail.com on 26 Oct 2014 at 11:25