Closed YasharF closed 5 years ago
It looks like besides sign-in by LinkedIn which provides the user's name and email address, the only other non-enterprise function that is remaining is sharing posts to LinkedIn on behalf of the user. Considering the current restrictions, it might be reasonable to remove the LinkedIn API example.
LinkedIn recently deprecated their API v1 in favor of v2. node-linkedin npm module has not been updated by its author in about two years and seems to be abandoned. passport-linkedin-oauth2 now supports the v2. The scope of this issue is to migrate off of node-linkedin while keeping passport-linkedin-oauth2 for obtaining tokens. passportjs configs may need some adjustments due to the new API, while the controller for the linkedin API example would need to be rewritten.
API v2 capabilities: https://www.linkedin.com/developers/products