search

google-code-export / gdata-python-client

Automatically exported from code.google.com/p/gdata-python-client
1 stars 0 forks source link

"Timestamp is too far from current time" when calling "UpgradeToOAuthAccessToken" #373

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I have been using OAuth + OpenID + AX in production for a long time now via
the gdata 1.0 client lib. The other day suddenly all my gdata api calls
began to fail with 401 Invalid Token errors. I cleared out all my stored
tokens, revoked authorization on a test account and tried to grant access
again. Now I am not able to upgrade a request token to an access token. It
always fails with the error "Timestamp is too far from current time". I am
not able to reproduce in my test environment. Both environments are using
the same version of the gdata library and both are using RSA (though with
different keys). The only difference is the ubuntu version. In production
it's 9.10, my test platform is running 10.04.

What steps will reproduce the problem?
Not clear as the same code works differently in two different environments.

What version of the product are you using?
gdata python client 2.0.10

Please let me know if there is any more information I can provide. I have a
lot of disappointed users at the moment. Thanks.

Original issue reported on code.google.com by elishac...@gmail.com on 30 May 2010 at 5:51

GoogleCodeExporter commented 9 years ago 
Great question Elisha, my first guess would be that your system clock is too 
far out of sync from the ones on Google servers. Is your clock set pretty close 
to the correct time?

Original comment by jscud.w...@gmail.com on 21 Jun 2010 at 5:26

GoogleCodeExporter commented 9 years ago 
yep. problem was in system and kernel clock.
I read this: http://en.gentoo-wiki.com/wiki/Time_Synchronization
than:
sudo htpdate -ds google.com;
sudo tzselect;
TZ='[SELECTED_TIME_ZONE]'; export TZ;
sudo hwclock --systohc

and that "time error" gone

Original comment by pigri...@gmail.com on 21 Jun 2010 at 6:08

GoogleCodeExporter commented 9 years ago 
Marking as closed.

Original comment by joe.gregorio@gmail.com on 10 Sep 2010 at 2:22

GoogleCodeExporter commented 9 years ago 
i also got the timestamp error when working with samples of the prediction-api.

simply setting the time correctly on my ubuntu vm that i was running oacurl 
from fixed the issue.

Original comment by daveccam...@gmail.com on 2 Aug 2011 at 6:40

GoogleCodeExporter commented 9 years ago 
"time error" gone too! Thanks!

Original comment by megajoe1...@gmail.com on 21 May 2013 at 11:22