Passes OAuth parameters as query parameters when getting access token #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This resolves an ongoing issue with the LinkedIn API where tokens were not functioning immediately after they were acquired. See: http://developer.linkedin.com/forum/unauthorized-invalid-or-expired-token-immediately-after-receiving-oauth2-token
|
Hi, I don't think the problem is in the client side. According to Lee Fu, LinkedIn Developer responsible for the API, the problem is due to the latency between servers after obtaining the access token. He is suggesting the clients to put a slight delay after obtaining the access token. |
|
I see – anyways, this fixed the issue I was having, and seemed consistent with the documentation. |
|
To get an AccessToken from LinkedIn by exchanging AuthCode, a GET request is preferred to POST request if you want the token being active immediately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves an ongoing issue with the LinkedIn API where tokens were not functioning immediately after they were acquired. See: http://developer.linkedin.com/forum/unauthorized-invalid-or-expired-token-immediately-after-receiving-oauth2-token
This also is consistent with the LinkedIn documentation: https://developer.linkedin.com/documents/authentication