---
title: Configuring an adapter instance
description: Configure the LinkedIn IdP Adapter to determine how PingFederate communicates with LinkedIn.
component: linkedin
page_id: linkedin:setup:pf_linkedin_cic_configuring_an_adapter_instance
canonical_url: https://docs.pingidentity.com/integrations/linkedin/setup/pf_linkedin_cic_configuring_an_adapter_instance.html
revdate: July 17, 2025
section_ids:
  steps: Steps
---

# Configuring an adapter instance

Configure the LinkedIn IdP Adapter to determine how PingFederate communicates with LinkedIn.

## Steps

1. In the PingFederate administrative console, go to **Authentication > Integration > IdP Adapters**. Click **Create New Instance**.

2. On the **Type** tab, set the basic adapter instance attributes.

   1. In the **Instance Name** field, enter a name for the adapter instance.

   2. In the **Instance ID** field, enter a unique identifier for the adapter instance.

   3. In the **Type** list, select **LinkedIn IdP Adapter**. Click **Next**.

3. (Optional) On the **IdP Adapter** screen, in the **Optional LinkedIn Attributes** section, define mappings between local attributes and the attributes from the core or extended contract.

   You can find a list of available attributes in [Core contract attributes](pf_linkedin_cic_core_contract_attributes.html).

   1. Click **Add a new row to 'Attribute Selector'**.

   2. In the **Local Attribute** field, enter the name of a local attribute.

   3. In the **LinkedIn Attribute** field, enter the JSON Pointer syntax for the value of the matching LinkedIn attribute.

      Learn more in [JSON Pointer syntax reference](pf_linkedin_cic_json_pointer_syntax_reference.html).

      |   |                                                                                            |
      | - | ------------------------------------------------------------------------------------------ |
      |   | The **Permissions** field on the **IdP Adapter** page determines the available attributes. |

   4. In the **Action** column, click **Update**.

   5. To add more attributes, repeat steps a - d.

4. On the **IdP Adapter** tab, configure the adapter instance by referring to [LinkedIn IdP Adapter settings](pf_linkedin_cic_linkedin_idp_adapter_settings.html). Click **Next**.

5. On the **Actions** tab, click **Test Connection**. Resolve any reported issues, then click **Next**.

6. On the **Extended Contract** tab, add the attributes that you want to include in the contract:

   1. Add the list of local attributes that you mapped on the **IdP Adapter** tab.

   2. Add any other LinkedIn attributes that you want to include in the contract.

      |   |                                                                                                                                                                                                                                                                                                         |
      | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | The values for unmapped LinkedIn attributes will be populated with raw JSON and could include arrays. You can find more information in [Object Types](https://docs.microsoft.com/en-us/linkedin/shared/references/v2/object-types?context=linkedin/consumer/context) in the LinkedIn API documentation. |

   3. Click **Next**

7. On the **Adapter Attributes** tab, set pseudonym and masking options as shown in [Set pseudonym and masking options](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_setting_pseudonym_masking_options.html) in the PingFederate documentation. Click **Next**.

8. On the **Adapter Contract Mapping** tab, configure the contract fulfillment details for the adapter as shown in [Define the IdP adapter contract](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_authnadapterinstancetasklet_plugincontractstate.html) in the PingFederate documentation. Click **Next**.

9. On the **Summary** tab, check and save your configuration.

10. If you created this adapter instance to replace a previous one, update the adapter mappings in any related service provider connections.