--- title: Configuring an adapter instance description: Configure the PingOne DaVinci IdP Adapter to determine how PingFederate communicates with PingOne DaVinci. component: pingone page_id: pingone:pingone_davinci_integration_kit:pf_p1_davinci_ik_configuring_an_adapter_instance canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_davinci_integration_kit/pf_p1_davinci_ik_configuring_an_adapter_instance.html revdate: June 19, 2024 section_ids: steps: Steps choose-from: Choose from: choose-from-2: Choose from: --- # Configuring an adapter instance Configure the PingOne DaVinci IdP Adapter to determine how PingFederate communicates with PingOne DaVinci. ## Steps 1. In the PingFederate administrative console, create a new IdP adapter instance: ### Choose from: * For PingFederate 10.1 or later: go to **Authentication > Integration > IdP Adapters**. Click **Create New Instance**. * For PingFederate 10.0 or earlier: go to **Identity Provider > 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 DaVinci IdP Adapter**. Click **Next**. 3. **Optional:** On the **IdP Adapter** screen, in the **Simple Parameter Mappings** section, select pre-defined parameters to send from PingFederate to DaVinci. | | | | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | The adapter sends your **Simple Parameter Mappings** and **Advanced Parameter Mappings** to DaVinci. In DaVinci, you can access these parameters by configuring your flow's input schema to expect the **DaVinci Parameter Name** values you define here. | | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | For more information about other input parameter options, see the [Parameter reference](https://download.pingidentity.com/public/documentation/pingfederate/11.0/sdkdoc/index.html?com/pingidentity/sdk/IdpAuthenticationAdapterV2.html) in the PingFederate SDK documentation and [Extended properties](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_extended_properti.html) in the PingFederate documentation. | 1. Click **Add a new row to 'Simple Parameter Mappings (optional)'**. 2. In the **Source** list, select the pre-defined parameter you want to send. 3. In the DaVinci **Attribute** field, enter a key name to use when sending the parameter to PingOne. 4. In the **Action** column, click **Update**. 5. To add more attributes, repeat steps a - d. 4. (Optional) On the **IdP Adapter** screen, in the **Advanced Parameter Mappings** section, define custom parameters to send from PingFederate to DaVinci. 1. Click **Add a new row to 'Advanced Parameter Mappings (optional)'**. 2. In the **Source Type** list, select the type of parameter you want to send. * Chained Attributes The attributes that are made available by other adapters and selectors in your PingFederate authentication policy. * Extended Properties These parameters store additional information about connections, OAuth clients, or both. You can find details in [Extended properties](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_extended_properti.html) in the PingFederate documentation. * Request Claims The claims PingFederate received within an OAuth/OpenID Connect Request Object or the parameters of a pushed authorization request. * Tracked HTTP Request Parameters The tracked HTTP request parameters that were included in the initial HTTP request of the current transaction. 3. In the **Source Parameter** field, enter the exact name of the parameter you want to send to DaVinci. The parameter must be available to the adapter from the **Source Type** that you selected. 4. In the **PingOne Attribute** field, enter a key name to use when sending the parameter to DaVinci. 5. In the **Action** column, click **Update**. 6. To add more attributes, repeat steps a-e. 5. (Optional) On the **IdP Adapter** screen, in the **DaVinci Response Mappings** section, map attributes from the PingOne response to the attribute contract. These attributes become available in your PingFederate authentication policy. | | | | - | ------------------------------------------------------------------------------------------------------------------------------ | | | Before using the table, check the **Extended Contract** tab to see which attributes are already included in the core contract. | 1. Click **Add a new row to 'DaVinci Response Mappings (optional)'**. 2. In the **Local Attribute** field, enter a name for the new attribute. 3. In the **DaVinci Attribute Mapping field**, enter the JSON Pointer syntax for the value of the matching PingOne attribute. For help, see [JSON Pointer syntax reference](pf_p1_davinci_ik_json_pointer_syntax_reference.html). 4. In the **Action** column, click **Update**. 5. To add more attributes, repeat steps a-d. 6. On the **IdP Adapter** screen, enter the values for **Company ID**, **Policy ID**, **API Key**, and **Subject Attribute Path**. | | | | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | You noted the values for **Company ID**, **Policy ID**, and **API Key** when you created the application in [Adding an application in DaVinci](pf_p1_davinci_ik_adding_an_application_in_davinci.html).In [Building a flow in DaVinci](pf_p1_davinci_ik_building_a_flow_in_davinci.html), you gave the **Name of the field containing the additional properties** field a value of `additionalProperties`. We added the `username` property to `additionalProperties`, so the **Subject Attribute Path** value becomes `/additionalProperties/username`. | 7. On the **Extended Contract** tab, add any **Local Attributes** that you added in the **DaVinci Response Mappings** table. Click **Next**. 8. 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**. 9. 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**. 10. On the **Summary** tab, check and save your configuration: ### Choose from: * For PingFederate 10.1 or later: click **Save**. * For PingFederate 10.0 or earlier: click **Done**. On the **Manage IdP Adapter Instances** tab, click **Save**.