-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid access token #77
Comments
same here |
@nvh95 any tips about that? |
same here |
Same here... Has anyone found a solution? |
Same here. This token doesn’t look right, check the value and try again. |
I have exactly the same issue. |
I have found an answer in the official linkedin authorization code flow documentation. This 211 character string that you're receiving is not the access token. It is an authorization code. Authorization code can be exchanged for an access token. To exchange it for an access token you can use linkedin-api-client library. |
Hi guys,
When I'm getting the access token using Postman I receive a 350 character long token.
When I'm doing it using
react-linkedin-login-oauth2
I receive a 211 character long token.There is a length difference between the 2, the one from Postman is longer.
When I use the Postman token to query
https://api.linkedin.com/v2/emailAddress?q=members&projection=(elements*(handle~))
it works properly but when I use the shorter token fromreact-linkedin-login-oauth2
I receive an error from linkedin:Any idea what I could be doing wrong?
Thanks
The text was updated successfully, but these errors were encountered: