Closed bravegag closed 8 years ago
I tested access with a standalone example using org.scribe and it works ... it does really seem some problem/misalignment with linkedin API in play-authenticate
I have same problem...
I've also come up against this error and really seems to be the problem of the linkedin provider. The problem is the following: reference.conf:93 requestTokenUrl="https://api.linkedin.com/uas/oauth/requestToken?scope=r_fullprofile+r_emailaddress"
This should be modified to (or overridden in mine.conf): requestTokenUrl="https://api.linkedin.com/uas/oauth/requestToken?scope=r_basicprofile+r_emailaddress"
Can anyone provide a patch that does not include changing the scope?
Sadly, LinkedIn changed its policy this year and this includes restricting the freely accessible profile info. To access full profile you need special login privileges: http://stackoverflow.com/questions/30115356/is-linkedin-api-allowing-to-access-all-user-profiles
I see. Sad times. Could you open a PR where you change the standard from what it is to a working link? On 1 Dec 2015 10:34 pm, "Akos Szabo" notifications@github.com wrote:
Sadly, LinkedIn changed its policy this year and this includes restricting the freely accessible profile info. To access full profile you need special login privileges:
http://stackoverflow.com/questions/30115356/is-linkedin-api-allowing-to-access-all-user-profiles
— Reply to this email directly or view it on GitHub https://github.com/joscha/play-authenticate/issues/284#issuecomment-160942173 .
Fixed via #289.
I enabled the linkedin in the play-usage example and I get the following exception/problem:
and the error message:
What's the issue? I have provided both the consumerKey and consumerSecret in the mine.conf file.