Topic-icon LinkedIn error 410

Active Subscriptions:

None
5 years 3 weeks ago #65295 by FunctionBay
Once I try to connect my profile account to LinkedIn I get the following error message on my website. Could you please help me to solve it! I´m using the latest Version of Joomla and JFBConnect as well as of Jomsocial. I followed the description for the set up of LinkedIn step by step.

Error code 410 received requesting data: { "errorCode": 0, "message": "This resource is no longer available under v1 APIs", "requestId": "549O2JVAZ6", "status": 410, "timestamp": 1554227259668 }.
Error code 410 received requesting data: { "errorCode": 0, "message": "This resource is no longer available under v1 APIs", "requestId": "YXJ7V2LY6X", "status": 410, "timestamp": 1554227259944 }.
We were unable to retrieve your LinkedIn account information. Please try again.

docs.microsoft.com/en-us/linkedin/consum...din/consumer/context
The topic has been locked.
Support Specialist
5 years 3 weeks ago #65299 by alzander
Replied by alzander on topic LinkedIn error 410
We're working on an updated release of JFBConnect that fully supports v2 of the LinkedIn API. However, version 1 should still work. We haven't seen the error that you're reporting, and the error doesn't provide any details on what call actually failed, which makes it difficult to understand what's actually going wrong there.

Can you try disabling the Social Profiles - JomSocial profile plugin and trying again? If you have any other profile plugins, try disabling those as well. If it still failes, that means some core functionality of authentication with LinkedIn is failing. If it works, it means the profile import ability is having issues. You can try to re-enable the profile plugins and then start removing specific fields from being imported. That will narrow down which specific profile field is causing issues.

Unfortunately, with v2 of LinkedIn's API, the amount of profile data we can import is extremely limited. It's likely any fields you're importing now will not be available with the upcoming update, so the work above may not be useful or necessary.

We're planning to release v8.1, which supports LinkedIn API v2, over the next week. At that point, it's likely the issue will clear up, but if not, we'll gladly help resolve any remaining issues.

I hope the above helps explain, but please keep us posted on what you determine.

Thanks,
Alex
The topic has been locked.