Skip to content

LINKEDIN.md

Latest commit

 

History

History
50 lines (38 loc) · 2.07 KB

LINKEDIN.md

File metadata and controls

50 lines (38 loc) · 2.07 KB

Table of Contents generated with DocToc

LinkedIn as authsource

LinkedIn recommends using OAuth2 and their v2 apis. Their v1 apis and OAuth1 endpoints are being shutdown. LinkedIn v2 apis return data in a more complex format (json keys change based on language) and require additional API calls to get an email address. You need to use the authoauth2:LinkedInV2Auth authsource since LinkedIn doesn't conform the expected OIDC/OAuth pattern.

Usage

   'linkedin' => [
        'authoauth2:LinkedInV2Auth',
        'clientId' => $apiKey,
        'clientSecret' =>  $apiSecret,
        // Adjust the scopes: default is to request email and liteprofile
        // 'scopes' => ['r_liteprofile'], 
    ],

Migrating from OAuth v1 authlinkedin

The authlinkedin module bundled with most versions of SSP uses deprecated OAuth v1 and v1 API endpoints. To migrate to the new LinkedIn API you will need to add a redirect URI to your linkedin application. The redirect URI is

https://hostname/SSP_PATH/module.php/authoauth2/linkback.php

You will then need to change your authsource configuration to match the example usage above.

On your IdP side you may need to use linkedin2name from this module rather than authlinkedin.

        // Convert linkedin names to ldap friendly names
        10 => array('class' => 'core:AttributeMap',  'authoauth2:linkedin2name'),

There are some minor changes in user experience and consent which are outlined in our blog post.