---
title: Configuring an adapter instance
description: Configure the Symantec VIP IdP adapter to allow PingFederate to use Symantec VIP as an authentication factor.
component: symantec-vip
page_id: symantec-vip:setup:pf_symantec_vip_ik_configuring_an_adapter_instance
canonical_url: https://docs.pingidentity.com/integrations/symantec-vip/setup/pf_symantec_vip_ik_configuring_an_adapter_instance.html
revdate: June 24, 2025
section_ids:
  steps: Steps
---

# Configuring an adapter instance

Configure the Symantec VIP IdP adapter to allow PingFederate to use Symantec VIP as an authentication factor.

## Steps

1. Sign on to the PingFederate administrative console.

2. On the **Identity Provider > Adapters** tab, click **Create New Instance**.

3. 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 **Symantec VIP Adapter**. Click **Next**.

4. On the **IdP Adapter** tab, configure the adapter instance by referring to [Symantec VIP IdP adapter settings reference](pf_symantec_vip_ik_symantec_vip_adapter_settings_reference.html). Click **Next**.

5. On the **Extended Contract** tab, add any attributes that you expect to retrieve in addition to the core contract attributes. Click **Next**.

6. Complete the adapter configuration.

7. On the **Summary** tab, check that the configuration is correct. Click **Done**.

8. On the **Manage IdP Adapter Instances** tab, click **Save**.

9. Modify your PingFederate authentication policy to pass attributes to your Symantec VIP IdP adapter instance from earlier in the authentication flow.

   The adapter expects the `username` attribute and accepts the optional security code attribute you defined in the **Security Code Attribute Name** field.

   Learn more about configuring authentication policies in [Authentication policies](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_authentication_policies.html) in the PingFederate documentation.
