---
title: IdP adapter instance configuration
description: After installing the OAM Integration Kit and the Access Server SDK library, you can configure your SP connection to use an instance of the OAM Adapter. The first part of this process is configuring the adapter instance.
component: oam
page_id: oam:setup:pf_oam_ik_idp_adapter_instance_configuration
canonical_url: https://docs.pingidentity.com/integrations/oam/setup/pf_oam_ik_idp_adapter_instance_configuration.html
revdate: July 5, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
  result: Result
---

# IdP adapter instance configuration

## About this task

After installing the OAM Integration Kit and the Access Server SDK library, you can configure your SP connection to use an instance of the OAM Adapter. The first part of this process is configuring the adapter instance.

## Steps

1. Log on to the PingFederate administrative console and click Adapters under IdP Configuration on the Main Menu screen.

2. On the Manage IdP Adapter Instances screen, click Create New Instance.

3. Enter the Adapter Name and Adapter ID. Select OAM 11g IdP Adapter 3.1.0 as the Adapter Type and click Next.

4. On the IdP Adapter screen, enter the values for adapter configuration as described on the screen and click Next.

   ![hss1563995550350](_images/hss1563995550350.png)

   |   |                                                                                                                                                                                                                                                                                       |
   | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | The Authentication Level Identifier is taken from the user's session token. The default/recommended value is authLevel. For the user's Authentication Level to be sent in the assertion, you must add the Authentication Level Identifier to the Adapter Contract (see step 5 below). |

5. Optionally, on the Extended Adapter Contract screen, you can configure additional attributes for the adapter. For instance, you can use the extended adapter contract for Policy Server response-object attributes. For more information, see [Extending an IdP adapter contract](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_extending_idp_adapter_contract.html) in the PingFederate documentation.

6. Click Next.

7. Select userId as the unique id. You may also select any extended attributes specified in the previous screen.

8. On the Summary screen, verify that the information is correct and click Done.

9. On the Manage Adapter Instances screen, click Save to complete the adapter configuration.

   ## Result

   You can now use this adapter instance for an SP connection. For information on setting up or modifying a connection, see [SP connection management](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_sp_connect_management.html) in the PingFederate documentation.