LinkedIn Access_Token Within Identity Is Incorrect

Anthony_Powers

November 2016 in Social Login

Identity\source\access_token from OneAll currently contains three keys

key (guid)
secret (guid)
date_expiration (date)

But LinkedIn does not use Key and Secret for Consumers. You use your LinkedIn App ID, LinkedIn App Secret, and Consumer Access Token. I'm not sure why OneAll is returning guid key and secrets here.

Can you please pass along the actual User Access_Token for LinkedIn like you do for the other Networks?

Thank you!

Answers

Anthony_PowersMember

November 2016

As you can see here (https://developer.linkedin.com/docs/oauth2) in Step 3, LinkedIn provides you a single access_token and the expires_in. You are parsing expires_in correctly, but something weird happens with access_token.
Claude_SchlesserAdministratorOneAll Team

November 2016

Hi Anthony,

I think this is because we use the legacy API, in that version the keys are different.
https://developer.linkedin.com/docs/oauth2-legacy

Adding the new token should however be no problem. I will check with our team and then get back to you!