OAuth timestamp_refused

52 posts / 0 new
Last post
Mudassir Mir's picture
Joined: 2009-11-25
Nov 28, 2009
OAuth timestamp_refused

Hi All,I am trying getting a timestamp_refused when I try to get a request token.oauth_acceptable_timestamps=1259424304215%2B-300000&oauth_problem=timestamp_refusedAnyone has any idea why is it saying this because the TimeStamp I am sending in the request is 1259424302342 which is well within the range of acceptable timestamp (1259424304215+-300000) by LinkedIn servers?Thanks,Mir

Anonymous (not verified)
Nov 28, 2009

Are you sending this timestampl explicit from your script? Or is it just server time that is allready included in your request?w

Jesper Joergensen's picture
Joined: 2009-11-26
Nov 28, 2009

I had the same problem. Timestamp should be *seconds* since Jan 1 1970, not *milliseconds*.Just divide your timestamp by 1000...

Anonymous (not verified)
Nov 30, 2009

This appears to be a bug in how we generate the error message.  We'll get that fixed.

Pandurang Zambare's picture
Joined: 2010-02-22
Feb 24, 2010

Hi allCan you guys let me know the solution to this problem .I am also experiencing similar issue -I am getting this oauth_acceptable_timestamps=1267003893%2B-300&oauth_problem=timestamp_refusedWhat needs to be done do resolve this problem.What is the intention behind responding with milisecond time timestamp here?Thanks

Anonymous (not verified)
Feb 24, 2010

Hi Pandurang,This means that your system clock is not in sync with our API servers by 5 minutes or more. The timestamp we give you indicates the range of times we would be expecting from you in your oauth_timestamp field. We also return the time to you in the body of the error message. While the time we take for an oauth_timestamp is to be in epoch seconds, we return to you epoch milliseconds just to confuse you. Simple division will get you back to seconds. We recommend using a stable NTP server to keep your clock in sync with us.Thanks,Taylor

Daniel Bahmani's picture
Joined: 2010-10-19
Oct 19, 2010

I change my system time to the time of the server(https://api.linkedin.com) by the header of the responseoauth_problem="timestamp_refused", oauth_acceptable_timestamps="1287551624+-300"and I got the same error, I mean "Error 400: bad request" with the same info at respose header againplease help me!!thanks in advance.

Daniel Bahmani's picture
Joined: 2010-10-19
Oct 21, 2010

I fixed it just by changing the method "WebResponseGet" in order to get the exe detail:try            {                responseReader = new StreamReader(webRequest.GetResponse().GetResponseStream());                responseData = responseReader.ReadToEnd();            }            catch (WebException exc)            {                exc.ToString();                HttpContext.Current.Response.Write(exc.Response.Headers.ToString());                using (WebResponse response = exc.Response)                {                    HttpWebResponse httpResponse = (HttpWebResponse)response;                    using (Stream data = response.GetResponseStream())                    {                        string text = new StreamReader(data).ReadToEnd();                        responseData = text;                        HttpContext.Current.Response.Write(TIMESPAN + "<br/><br/>" + text + "<br/><br/>");                    }                }                //throw;            }and then TIMESPAN is the value of time stamp generated in the GenerateTimeStamp method.I checked my timestamp with the acceptable timestamp byhttp://javascript.internet.com/math-related/unix-date-time-converter.html I found there is 3 hours diffrence time. so I chenged GenerateTimeStamp to the following and it worksTimeSpan ts = DateTime.UtcNow.AddHours(-3) - new DateTime(year, month, day, hour, min, 0, 0, 0);

Anurag Trivedi's picture
Joined: 2011-05-15
May 15, 2011

Hi Daniel,Where i make this changes .sorry i am unable to find out code where i makes your suggested code.Actually i am also same error.Request token retrieval failed:RESPONSE:

Array(    [linkedin] => Array        (            [oauth_problem] => timestamp_refused            [oauth_acceptable_timestamps] => 1305527348+-300        )

Plz help me out.But its surpise that in my local machine its working fine.

Anurag Trivedi's picture
Joined: 2011-05-15
May 16, 2011

Hi,Timestamp or date format is same on my live server and local machine, but its working fine on local machine.Timestamp is IST in both localhost and on live server.And more thing its not possible to change test server setting for particlar API call ,its effect in all other runnung site.Below responese i get .Request token retrieval failed:RESPONSE:Array(    [linkedin] => Array        (            [oauth_problem] => timestamp_refused            [oauth_acceptable_timestamps] => 1305529586+-300        )    [info] => Array        (            [url] => https://api.linkedin.com/uas/oauth/requestToken            [content_type] => application/x-www-form-urlencoded;charset=UTF-8            [http_code] => 400            [header_size] => 365            [request_size] => 595            [filetime] => -1            [ssl_verify_result] => -8179            [redirect_count] => 0            [total_time] => 0.274449            [namelookup_time] => 0.059531            [connect_time] => 0.105213            [pretransfer_time] => 0.226635            [size_upload] => 0            [size_download] => 77            [speed_download] => 280            [speed_upload] => 0            [download_content_length] => 77            [upload_content_length] => 0            [starttransfer_time] => 0.274373            [redirect_time] => 0        )    [oauth] => Array        (            [header] => Authorization: OAuth realm="http%3A%2F%2Fapi.linkedin.com",oauth_version="1.0",oauth_nonce="0a2ee1b2e4bfd298a30d7ca58eb83a72",oauth_timestamp="1305528690",oauth_consumer_key="c41R4iVkinkrNCkS2UtQPKnuWhKWEtyvE3eIBPT73wih1Wz8f8c3AgkabSi6diWl",oauth_callback="http%3A%2F%2Fwebmedia.websoftware.com%2Fexamplesite%2Fexamplesite%2Flinkphp%2Fdemo.php%3FlType%3Dinitiate%26lResponse%3D1",oauth_signature_method="HMAC-SHA1",oauth_signature="KYWz%2FIxVLX9pX7%2Fi9ctVhN1POYs%3D"            [string] => POST&https%3A%2F%2Fapi.linkedin.com%2Fuas%2Foauth%2FrequestToken&oauth_callback%3Dhttp%253A%252F%252Ftekmedia.tekritisoftware.com%252Fandroidicebreaker%252Fexamples%252Flinkphp%252Fdemo.php%253FlType%253Dinitiate%2526lResponse%253D1%26oauth_consumer_key%3Dc41R4iVkinkrNCkS2UtQPKnuWhKWEtyvE3eIBPT73wih1Wz8f8c3AgkabSi6diWl%26oauth_nonce%3D0a2ee1b2e4bfd298a30d7ca58eb83a72%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1305528690%26oauth_version%3D1.0        )    [error] => OAuth callback url was not confirmed by the LinkedIn end-point    [success] => )LINKEDIN OBJ:LinkedIn Object(    [callback:protected] => http://webmedia.websoftware.com/examplesite/examples/linkphp/demo.php?lType=initiate&lResponse=1    [token_access:protected] =>     [token_request:protected] =>     [application_key:protected] => c41R4iVkinkrNCkS2UtQPKnuWhKWEtyvE3eIBPT73wih1Wz8f8c3AgkabSi6diWl    [application_secret:protected] => mDuM8RqZlLQjtvHPisewNw2QSUSbbhmITb6qBWWOeDNuKcXD1xXUNQF3VX4Pxs2r    [response_format:protected] => xml)

Kirsten Hunter's picture
Joined: 2011-06-30
May 16, 2011

If you look at the call you can clearly see that the timestamp you're sending is outside of the bounds required by the OAuth server.[oauth_problem] => timestamp_refused            [oauth_acceptable_timestamps] => 1305529586+-300POST&https%3A%2F%2Fapi.linkedin.com%2Fuas%2Foauth%2FrequestToken&oauth_callback%3Dhttp%253A%252F%252Ftekmedia.tekritisoftware.com%252Fandroidicebreaker%252Fexamples%252Flinkphp%252Fdemo.php%253FlType%253Dinitiate%2526lResponse%253D1%26oauth_consumer_key%3Dc41R4iVkinkrNCkS2UtQPKnuWhKWEtyvE3eIBPT73wih1Wz8f8c3AgkabSi6diWl%26oauth_nonce%3D0a2ee1b2e4bfd298a30d7ca58eb83a72%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1305528690%26oauth_version%3D1.01305528690 is not within 300 of 1305529586.I'm not sure why your system is creating an incorrect timestamp if, as you say, it's set correctly.  OAuth requires that the timestamp on your server be within the correct boundaries for the server you're using.You need to work with your system and see why the PHP library is setting the wrong timestamp.  While the timezone may be the same, if the server is not syncing to an NTP server (or is syncing to an incorrect one) it can get out of sync.

Vasudevan Thirunavukkarasu's picture
Joined: 2010-12-23
Apr 15, 2011

Hi,  I too face the same problem. I constantly receive 1299484140000 for currentStatusTimestamp. I can't use this value to find the time difference between linkedin and my server. Any help?Regards,Vasu

Kirsten Hunter's picture
Joined: 2011-06-30
Apr 18, 2011

If you share the language/library/code you're using it might help. It sounds like the method you're using isn't actually giving you an accurate timestamp, though.

Joined: 2011-05-11
May 11, 2011

I set the time of my server correctly and it worked.

Joined: 2011-06-08
Jun 8, 2011

hi ,Iam doing on my local system with out any server or proxy then how and where i need to correct time.......?

Kirsten Hunter's picture
Joined: 2011-06-30
Jun 8, 2011

Your system has a clock, and the timestamp will be generated based on that.

Joined: 2011-06-08
Jun 8, 2011

Hi kirsten jones,  here iam sending you the exception message what i got. i am following the login example with signpost given by tayloroauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: Server returned HTTP response code: 400 for URL: https://api.linkedin.com/uas/oauth/requestToken?oauth_callback=oob        at oauth.signpost.basic.DefaultOAuthProvider.retrieveToken(DefaultOAuthProvider.java:150)        at oauth.signpost.basic.DefaultOAuthProvider.retrieveRequestToken(DefaultOAuthProvider.java:66)        at SignPost.main(SignPost.java:32)Caused by: java.io.IOException: Server returned HTTP response code: 400 for URL: https://api.linkedin.com/uas/oauth/requestToken?oauth_callback=oob        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)        at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1496)        at java.security.AccessController.doPrivileged(Native Method)        at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1490)        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1144)        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)        at oauth.signpost.basic.DefaultOAuthProvider.retrieveToken(DefaultOAuthProvider.java:129)        ... 2 moreCaused by: java.io.IOException: Server returned HTTP response code: 400 for URL: https://api.linkedin.com/uas/oauth/requestToken?oauth_callback=oob        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)        at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)        at oauth.signpost.basic.DefaultOAuthProvider.retrieveToken(DefaultOAuthProvider.java:123)        ... 2 moreplease help me out and here iam attaching my source file too.Regards,Rajeshk

Vinay Simha Raju Peddiraju's picture
Joined: 2011-09-22
Sep 25, 2011

Hello Pandurang...Even I am facing the same problem..have u got the solution pls send me detail so that I can come out of this problem..

Pls help me..I am frustrated about this from long back.

Thanks,
Vinay

Vinay Simha Raju Peddiraju's picture
Joined: 2011-09-22
Sep 26, 2011

Hi taylor,
Please help me out..I am facing a problem when I am requesting for the AuthorizationLink.

let me know the solution to this problem .I am experiencing a issue -I am getting this oauth_acceptable_timestamps=1267003893%2B-300&oauth_problem=timestamp_refusedWhat needs to be done do resolve this problem.What is the intention behind responding with milisecond time timestamp here?Thanks

Kirsten Hunter's picture
Joined: 2011-06-30
Sep 26, 2011

Generally you can simply check what the system time is on your server - it should be using an NTP server to stay up-to-date. If you want to ask our servers, you can - here's an example of doing it in php:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
<?php
 
function get_linkedin_current_time() {
                date_default_timezone_set("America/Los_Angeles");
               
                $ch = curl_init("http://api.linkedin.com");
                curl_setopt($ch, CURLOPT_HEADER, true);
                curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
                curl_setopt($ch, CURLOPT_NOBODY, true);
 
                $response = curl_exec($ch);
                foreach(explode("\r\n", $response) as $line) {
                                if(substr($line, 0, 5) == "Date:") {
                                                return strtotime(trim(substr($line, 5)));
                                }
                }
 
                return -1;
}
 
printf("Local time deviates from LinkedIn time by: %d seconds", get_linkedin_current_time() - time());
 
?>
[php]
- -
Joined: 2011-12-01
Jan 9, 2012

Is there /any/ way to make Linkedin less harsh on the timestamp boundaries? My server differs with about 400 seconds -too much- and I don't have access to change server settings. Would hate to abandon Linkedin apps because of this...

Kirsten Hunter's picture
Joined: 2011-06-30
Jan 10, 2012

The OAuth standard specifies that the timestamp is important, and extending it for your particular case would just mean that someone else would come along who needed more seconds. You can grab the time from another API (unfortunately, we don't have an unsigned clock request) - Netflix has one, for instance.

John Pattinson's picture
Joined: 2011-06-28
Feb 15, 2012

I am still getting the same error:
Caused by: org.scribe.exceptions.OAuthException: Response body is incorrect. Can't extract token and secret from this: 'oauth_problem=timestamp_refused&oauth_acceptable_timestamps=1329300480%2B-300'
after execution of below code line:-
requestToken = service.getRequestToken();

What should I do?

Kirsten Hunter's picture
Joined: 2011-06-30
Feb 15, 2012

You need to fix the time on your server so that it's accurate.

John Pattinson's picture
Joined: 2011-06-28
Feb 15, 2012

I don't have any server of mine. I am tring to get request token for IlinkedIn account. As a third party developer, I don't have any control on LinkedIn server.

Addon to this statement, I would like to tell you that same code was working for me yesterday by afternoon but then it stopped working.

Steven Citron-Pousty's picture
Joined: 2011-08-02
Feb 16, 2012

John:
You really do need to include sample code that you are trying to run, http headers for both the request and the response, the URLs, and the response body. I also suggest you complete the getting started tutorial for the REST API. Those things should help you on your way.
Thanks
Steve

John Pattinson's picture
Joined: 2011-06-28
Feb 16, 2012

Thanks steve, The code, I am using is here:
Line 1: service = new ServiceBuilder().provider(LinkedInApi.class).apiKey("xyz").apiSecret("abc").build();
Line 2: requestToken = service.getRequestToken();

My app is getting crashed at Line No. 2 with an error written here:
E/AndroidRuntime(232): Caused by: org.scribe.exceptions.OAuthException: Response body is incorrect. Can't extract token and secret from this: 'oauth_problem=timestamp_refused&oauth_acceptable_timestamps=1329460881%2B-300'

I had used another way to get Request token, code for that is here:
Line 1: oauthService = LinkedInOAuthServiceFactory.getInstance().createLinkedInOAuthService(consumerKeyValue,consumerSecretValue);
Line 2: requestToken = oauthService.getOAuthRequestToken(OAUTH_CALLBACK_URL);

Even by this, Same crash is observed at Line no. 2 while getting request token.

Note: Code was working fine two days before, but not now.

Simon Grantham's picture
Joined: 2011-11-17
Feb 17, 2012

You cannot effectively use the API if you cannot set or have someone set the time accurately. All processor clocks drift after a while and the drift rate varies by individual machine. This means that even if you set the time accurately, after a period of time, it will drift outside of the 5 minute window and your application will stop working and you will be scratching your head to figure out why.

If you're on a Windows server and you have admin rights, you can synchronize to time.windows.com by double clicking your time display, click on change settings if windows 7 and then select internet time tab.

If you're on a linux server, and of course, have sudo access, you can synch to ntp.org by installing ntp (sudo apt-get install ntp).

Abhishek Dixit's picture
Joined: 2012-03-14
Mar 17, 2012

Hi KJ,

I am an Android developer struggling to make LI APIS to work on android handhelds. I am using a library called linkedin-j which is the mentioned on the LI website also. Now this library works fine on most of the devices but fails to work on couple of handsets.

To solve this I wrote my own code to get the request token which also worked fine on all the devices but still failed on the same subset of devices on which even the library calls were failing.

I get a vague exception: FileNotFoundException.

Now during writing my own code to fetch the request token I realized that even if I miss a comma while forming the "Authorization" header string it gives me same vague exception rather than a more specific pointer to the actual cause.

Can you please let me know if there is something I can try or something I should look at? My requests and signature are perfect. I verified the same on LinkedIn OAuth Test Console also.

Also one more strange behavior I observed. My app was previously not working on my Acer Iconia Android Tablet. Then I changed the Date/Time to Set Based on Network and then everything just worked fine. I felt that this could be the issue related to the TimeStamp stuff but then I changed the values back to some different time zone but the application still works.

Any help would be highly appreciated.

Thanks,
Abhishek.

Abhishek Dixit's picture
Joined: 2012-03-14
Mar 17, 2012

Hi KJ,

I got the solution to my problem right after submitting the comment. It was a problem related to Timestamp. I did not noticed that apart from the wrong time my device was showing a wrong Date also. Changing it to current date and time based on network settings the thing are perfect now.

But I have a new question now.

Does the LI (LinkedIn) server make out the exact timestamp or lets say the time zone of the location from where the request has originated?

If Yes, then does it compare the time calculated based on the time zone detected in the previous step and verifies the sent time stamp against the calculated time ?

DetectedTime (In 1st Step) - TimeStamp(in seconds) sent in the request < 300 seconds

I just want to know if my understanding is right so that this entire bug solving Session can be a good Lesson for me :).

Thanks,
Abhishek

Joined: 2012-03-19
Mar 23, 2012

I'm having this same problem, but I'm using Zend Framework to do this OAuth part. Looks like our server is about 5 minutes fast. I'm unable to reset the time on our server because I'm not a system administrator, but I can set it at runtime. I've tried resetting the time (subtracting from it) in both PHP and Zend Framework at runtime, but LInkedIN is still giving me this same error, so I'm assuming I'm not resetting the timestamp correctly. Does anyone know how I can fix this problem in Zend Framework?

Abhishek Dixit's picture
Joined: 2012-03-14
Mar 26, 2012

Hi,

This cannot be fixed just by changing the time stamp value or manipulating it. As per my understanding there are 2 things to consider:

1. The system's timezone : Maybe the Linked Server detects your time zone based on your IP or some way which is always your actual timezone so you should respect that :).

2. Time expected as per the timezone.

For Example: If timezone is TZ1 and as per that the time should be Time1 then that should be the time stamp sent to the server.

Now if this is not within 5 mins range then it will fail as the LI server will think it to be an old request.

Now the only thing u need to do is to get the server's time zone by identifying it's IP or some other way and then set your time stamp based on that.

Jeremy Johnstone's picture
Joined: 2011-04-17
Mar 27, 2012

Hello All,

The timestamp is a "unix timestamp". As such, the timezone is irrelevant because unix timestamp is defined as the number of seconds since January 1st, 1970 in GMT. So as long as your server's clock is:

1) Set to a correct value (you should use NTP!)
2) The server knows what timezone it's clock is set to

Then you will get a correct timestamp value.

-Jeremy

Joined: 2012-04-12
Apr 13, 2012

Yes Indeed. I confirm System clock has somthing to do with this.
I set my time to Windows server time (synchro).

It works Thanks.

Anuj Acharya's picture
Joined: 2011-09-28
Apr 25, 2012

timestamp_refused
error from pyhton code..What is wrong with linkedin?

Kirsten Hunter's picture
Joined: 2011-06-30
Apr 26, 2012

There is nothing wrong with LinkedIn. The timestamp your server is generating is incorrect.

Marco Aurelio Guado Zavaleta's picture
Joined: 2011-09-04
May 14, 2012

Problem:
StandardWrapperValve[Extraer]: PWC1406: Servlet.service() for servlet Extraer threw exception org.scribe.exceptions.OAuthException: Response body is incorrect. Can't extract token and secret from this: 'oauth_problem=timestamp_refused&oauth_acceptable_timestamps=1336984074%2B-300' at org.scribe.extractors...
//**************************************
Solution:
Check the time of the BIOS and SYSTEM, comand linux-Debian
prompt$>hwclock --systohc
prompt$>hwclock --show

The next step, install ntp
prompt$>apt-get install ntp

Ready to run your code and you'll get your permit validated. Okey.

Ananda Subasinghe's picture
Joined: 2011-08-01
Jun 28, 2012

timestamp_refused with python
I am also getting the same error. It should be a something wrong with linkedin.

Marco Aurelio Guado Zavaleta's picture
Joined: 2011-09-04
Jun 29, 2012

Usually the problem of time is because, when the servers are synchronized times are not correct, it first checks the time and then develop in Python.

Mohammed Gomma gomma's picture
Joined: 2012-06-20
Jun 30, 2012

try to match your time with linkedin response

Joined: 2012-08-28
Aug 31, 2012

what i need to change in server, i mean time format or anything else , Please help me

Joined: 2012-08-28
Aug 31, 2012

how can i find my server is generating incorrect timestamp, Please tell me how can i match the timestamp with linkenIn and how can i set the timestamp in my server.

Adam Trachtenberg's picture
LinkedIn Employee
Joined: 2011-06-30
Aug 31, 2012

Use ntp to keep your clock in sync with the rest of the world.

Joined: 2011-11-10
Sep 18, 2012

You are right
Time of local machine (for developer) or server should match the current time of their timezone.

Joined: 2012-06-01
Oct 4, 2012

Hi I'm Albert

I just programing an android application And I want to log in LinkedIn but I always have and error on this line: liToken = oAuthService.getOAuthRequestToken(OAUTH_CALLBACK_URL);

and the error are theese:

E/AndroidRuntime(17661): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.tenea.linkedin/com.tenea.linkedin.LinkedinActivity}: com.google.code.linkedinapi.client.oauth.LinkedInOAuthServiceException: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: https://api.linkedin.com/uas/oauth/requestToken
.
.
E/AndroidRuntime(17661): Caused by: com.google.code.linkedinapi.client.oauth.LinkedInOAuthServiceException: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: https://api.linkedin.com/uas/oauth/requestToken
.
.
E/AndroidRuntime(17661): Caused by: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: https://api.linkedin.com/uas/oauth/requestToken
.
.
E/AndroidRuntime(17661): Caused by: java.io.FileNotFoundException: https://api.linkedin.com/uas/oauth/requestToken

I don't know why, I was reading something about timeStamp and seconds since 1970 but I didn't really understand and I don't know how to implement this on my code.. I don't know from where I have to get de timeStamp and how do it..

I'm using eclipse running over Windows

if some can help me please I'm really tired with this problem but it's important for me, please help me.

Joined: 2012-06-01
Oct 5, 2012

Hi I have the same problem that you, can you tell me how you solve it??

I'm using scribe 1.3 library and my timestamp is not correct and I don't know how to solve it..

Token requestToken = service.getRequestToken(); in this line my android app crashes

please help me, thanks for advance.

Satish Pandey's picture
Joined: 2011-10-24
Oct 12, 2012

I used following commands to get it working on CentOS (Linux) :
$ yum install ntp
$ ntpdate pool.ntp.org
$ /etc/init.d/ntpd start

Joined: 2012-10-29
Nov 1, 2012

Hi,
i also have that problem, so i decided to retrieve the timestamp from the linkein response then make another request with retrieved timestamp.
it works for me. i didn't check that if second request has delay, what happened for that !

Deepak K's picture
Joined: 2012-11-16
Nov 20, 2012

Hi Kristen,

I was getting the same error when I tried to login to linkedin using the Hybridauth plugin. The Hybridauth was showing the error as "Authentification Failed: Invalid Access Token", but I fixed that by adjusting the server time. Now when I click login button it is getting redirected to linkedin app login page, but after login it is redirecting to hybridauth app and is showing the "Authentification Failed: Invalid Access Token" message.

What could be the issue? Can you please help me to fix this

jitendra patel's picture
Joined: 2013-03-12
Mar 24, 2013

Please see the time and date (timestamp) of your local machine/server.....may be mismatch......change your timestamp this issue may resolved....

Baltazar Zaraik's picture
Joined: 2013-07-12
Jul 15, 2013

have the same problem on Drupal 7, i dont know what it is. Any ideas?

"Message Linkedin reported the following response : timestamp_refused"

My LinkedIn account is from Argentina and the website is in USA servers, is there a problem?

Thanks for your help!

Pages