-
Notifications
You must be signed in to change notification settings - Fork 109
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
InternalOAuthError: failed to fetch user profile #75
Comments
ok. verified that the problem is with this module that has not been updated to linkedin API 2.0 as reported in this issue:_ #24 |
This fork has a fix for the problem: https://github.com/sokratisvidros/passport-linkedin-oauth2 |
IS there a reason why this only supports r_lite_profiles now? |
Sokratisvidros's works for me and I'm using it without a session. Thanks |
@trungtangg Yeah I think you were right. All I have to do is change r_basicprofile to r_liteprofile to make it work. |
For me, the solution suggested in this comment solved the issue: #102 (comment) |
add "openid" in scope, it will work passport.use(new LinkedinStrategy({ }, |
So today, out of the blue this error appeared. On my app, that has been using linkedin singin since 2011. I have the latest version of passport-linkedin-oauth2, everything seems correct in the app settings in linkedin developer page... Any ideas what can produce this error? Seems somehow related to the API 1.0 deprecation, but what do we need in order to comply? since we were using OAuth2 already for years I did not think any action needs to be taken...
If somebody has a hint I really appreciate a prompt response, no customer can login in the system using linkedin which is quite a severe issue :/.
The text was updated successfully, but these errors were encountered: