oauth token rejected issues about linkedin HOT 19 CLOSED

I had the same error when i passed access token/secret into authorize_from_request method instead of request token/secret. Make sure youre passing the right values.

from linkedin.

Thanks vladgurovich, but that isn't our issue. The failures are intermittent, which wouldn't happen if we were using the wrong values.

from linkedin.

I'm having the same problem, following the tutorial line for line and double checking my tokens. Did you ever figure it out?

from linkedin.

We are still experiencing the issue occasionally. I haven't been able to figure out any pattern for failures either.

from linkedin.

We're having the same issue here. Sometimes we receive this same error and impossible to figure out where does it come from...

from linkedin.

I run the LinkedIn Developer Network. Sorry about this. We fixed a bug, but introduced another in the process. :( We're working to fix the new bug. I'll post another comment when the patch is live.

from linkedin.

This should now be fixed. Let us know if you still have the problem. Thanks for your patience.

from linkedin.

Wow, that is awesome that folks at LinkedIn Developer Network are paying attention to support issues here. I'll let you know if the issue persists.

from linkedin.

I concur, thanks guys!

from linkedin.

Glad we were able to fix this! In the future, best way to let us know about issue that you think might be our problem (as in, it used to work fine, but now lots of people are reporting errors for code that hasn't changed) is to post a message on the http://developer.linkedin.com forums. We also monitor @linkedindev (but it's hard to provide a good bug report in 140 characters).

from linkedin.

It looks like the issue has resurfaced. This weekend (starting on 8/13/2011) I started seeing "OAuth::Problem: token_rejected" errors again. It looks like LinkedIn is aware, https://developer.linkedin.com/forum/clientauthorizefromrequest-works-localhost-not-production#comment-7673.

from linkedin.

hey, i'm using linkedin gem for my RoR application, it's running fine on my local and stagign(it's live with dummy data only for testing) but on Production i'm having Oauth::timestamp refused error. My Staging and Production servers are using +0000 zone settings and i have no idea how to resolve this thing. Please let me know how to fix this.

from linkedin.

Check your system clock. It is off.

from linkedin.

Looks like this sorted itself out :)

from linkedin.

We are facing the same issue. Is something broken again ? We are running on scribe v1.3.5

from linkedin.

@javapriyan any more information would be useful. I have no clue out of context 😄s

from linkedin.

Often I get this 'oauth_problem=token_rejected' issue. Here is the stack trace.http://paste.opensuse.org/57675457

from linkedin.

@javapriyan Are you sure you're asking the right repo? This repo is the ruby linkedin library.

Really it seems like you'd have better luck asking the linkedin developer forum or scribe about the specific issue. Also without seeing the source code I have no idea what the issue could be.

Thanks 😄

from linkedin.

@hexgnu Oh my bad. Wrong room :) Thanks.

from linkedin.