---
title: Configuring an adapter instance
description: Configure the PingOne Credentials IdP Adapter to determine how PingFederate communicates with PingOne Credentials.
component: pingone-credentials
page_id: pingone-credentials:setup:pf_p1_credentials_ik_configuring_an_adapter_instance
canonical_url: https://docs.pingidentity.com/integrations/pingone-credentials/setup/pf_p1_credentials_ik_configuring_an_adapter_instance.html
revdate: September 3, 2024
section_ids:
  steps: Steps
  example: Example:
  example-2: Example:
  example-3: Example:
  next-steps: Next steps
---

# Configuring an adapter instance

Configure the PingOne Credentials IdP Adapter to determine how PingFederate communicates with PingOne Credentials.

## 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. From the **Type** list, select **PingOne Credentials IdP Adapter**. Click **Next**.

3. On the **IdP Adapter** tab, in the **Credential Types and Attributes** section, define the credential types and attributes that you want users to present for verification.

   1. Click **Add a new row to 'Credential Types and Attributes'**.

   2. In the **Credential Type** list, select a credential type that you want users to present for verification.

      ### Example:

      `verifiedEmployee`

   3. In the corresponding **Credential Attribute** field, enter any attributes that you want users to present for verification.

      Separate the attribute values with commas.

      ### Example:

      `firstName, lastName`

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

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

   Because the credential issuer and credential verifier can be in different environments, the **Credential Type** list doesn't auto-populate credential types for the selected environment. Use the following issuer filters, **Requested Issuer(s) by Environment ID** and **Requested Issuer(s) by Decentralized Identifiers (DID)** to filter through environments and find the credential types that you want to include in the credential presentation request.

4. **Optional:** In the **Requested Issuer(s) by Environment ID** section, enter the PingOne environment ID of a trusted issuer.

   1. Click **Add a new row to 'Requested Issuer(s) by Environment ID'**.

   2. In the **Issuer by Environment ID** field, enter the environment ID of the issuer.

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

   4. To add more issuers, repeat steps a-d.

5. **Optional:** In the **Requested Issuer(s) by Decentralized Identifiers (DID)** section, enter the decentralized identifier of a trusted issuer.

   1. Click **Add a new row to 'Requested Issuer(s) by Decentralized Identifiers (DID)'**.

   2. In the **Issuer by Decentralized Identifier** field, enter the decentralized identifier of the issuer.

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

   4. To add more issuers, repeat steps a-d.

6. On the **IdP Adapter** tab, configure the adapter instance by referring to [PingOne Credentials IdP Adapter settings reference](pf_p1_credentials_ik_p1_credentials_idp_adapter_settings_reference.html). Click **Next**.

7. On the **Extended Contract** tab, add all of the attributes that you defined in the **Credential Types and Attributes** table. Then click **Next**.

   Using the following format, define each attribute separately:

   ```
   <credentialType>.<credentialAttribute>
   ```

   ### Example:

   For a `verifiedEmployee` credential type that has two attributes, entered in the **Credential Attribute** field as `firstName, lastName`, add the `firstName` attribute first:

   ```
   verifiedEmployee.firstName
   ```

   Then add the `lastName` attribute:

   ```
   verifiedEmployee.lastName
   ```

8. On the **Adapter Attributes** tab, for **subject**, select the **Pseudonym** check box. Click **Next**.

9. On the **Adapter Contract Mapping** tab, click **Configure Adapter Contract** and fill out the configuration as necessary. Click **Done**, then **Next**.

   |   |                                                                                                                                                                                                                                               |
   | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | Make sure to click **Configure Adapter Contract** and complete a configuration, even if it's just **Configure Adapter Contract > Next > Next > Next > Done > Next**. Otherwise, the adapter contract fulfillment isn't mapped to the adapter. |

10. On the **Summary** tab, review your configuration. Click **Save**.

## Next steps

Complete the [Extending the contract](pf_p1_credentials_ik_configuring_the_extended_contract.html) procedure.