We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A community member raised this support ticket reporting a problem with LinkedIn integration: This resource is no longer available under v1 APIs
the linkedin lib bundled with Gluu already uses the v2 urls, but still we need to validate and adjust if needed.
@sahiliamsso can you validate if this is hapenning in the 4.0 tests you are doing?
The text was updated successfully, but these errors were encountered:
It is reproducible in latest 4.0
2019-06-19T22:58:40.688Z [ERROR] Unknown Error: InternalOAuthError: failed to fetch user profile (status: 410 data: { "errorCode": 0, "message": "This resource is no longer available under v1 APIs", "requestId": "T0931U9JX8", "status": 410, "timestamp": 1560985120664 })
Sorry, something went wrong.
It's due to changes in LinkedIn API and auht0's passport-linkedin-oauth2 apparently not being maintained
Some pointers: auth0/passport-linkedin-oauth2#77 auth0/passport-linkedin-oauth2#75 auth0/passport-linkedin-oauth2#63
Checking if we can use this strategy now: https://github.com/sokratisvidros/passport-linkedin-oauth2/
I tested and we can use sokratisvidros repo
I'm awaiting input from SokratisVidros/passport-linkedin-oauth2#2 and will proceed
Project adjustments for #62
bff25fe
#62
1bb92ea
jgomer2001
sahilIT2020
No branches or pull requests
A community member raised this support ticket reporting a problem with LinkedIn integration: This resource is no longer available under v1 APIs
the linkedin lib bundled with Gluu already uses the v2 urls, but still we need to validate and adjust if needed.
@sahiliamsso can you validate if this is hapenning in the 4.0 tests you are doing?
The text was updated successfully, but these errors were encountered: