LinkedIn Login Integration Kit

Upgrading an existing deployment

If you’re upgrading from a previous version of the LinkedIn Login Integration Kit, you might need to take extra steps.

Steps

  1. Back up your current PingFederate configuration as shown in Configuration archive in the PingFederate documentation.

  2. If you’re upgrading from LinkedIn IdP Adapter 2.2 or earlier:

    1. Note your adapter instance configuration.

    2. Delete the adapter instance.

    3. Complete the steps in Deploying the integration files.

    4. Complete the steps in Configuring an adapter instance. Configure the adapter instance settings based on your notes, making the following changes:

    Update the LinkedIn User Data v2 URL field

    • Related Change: The https://api.linkedin.com/v2/me API endpoint that the LinkedIn IdP Adapter used to retrieve user information in LinkedIn Login Integration Kit 2.2 and earlier is now unavailable.

    • Required Action: When you upgrade the LinkedIn IdP Adapter, make sure the LinkedIn User Data v2 URL field contains the new API URL, https://api.linkedin.com/v2/userinfo. Learn more in LinkedIn IdP Adapter settings.

    Update the Permissions field

    • Related Change: The API endpoint that the LinkedIn IdP Adapter used to retrieve email addresses is now unavailable. As a result, LinkedIn Login Integration Kit 3.0 has deprecated the LinkedIn User Email V2 URL field and the r_emailadress, r_liteprofile, and r_fullprofile permissions.

    • Required Action: Make sure the Permissions field contains the new default permissions, profile, openid, and email. Learn more in LinkedIn IdP Adapter settings.

      Additionally, you can find a sample user information payload using the new API URL and permissions in JSON Pointer syntax reference.

    Check Optional LinkedIn Attributes

    • Related Change: If you mapped any attributes in the Optional LinkedIn Attributes section when configuring an adapter instance, your configuration might be broken or no longer relevant.

    • Required Action: Review your adapter configuration and fix any errors reported during the connection test. Learn more in Configuring an adapter instance.

    Update any configurations using the id core contract attribute

    • Related Change: LinkedIn Login Integration Kit 3.0 has replaced the id core contract attribute with the sub core contract attribute to align with the response body schema described in Sign In with LinkedIn using OpenID Connect.

    • Required Action: Review your authentication policy and connection configuration. Change all instances of id to sub. Learn more in Core contract attributes.