---
title: Configuring an adapter instance
description: Configure the CrowdStrike IdP Adapter to determine how PingFederate communicates with CrowdStrike.
component: crowdstrike
page_id: crowdstrike:setup:pf_crowdstrike_ik_configuring_an_adapter_instance
canonical_url: https://docs.pingidentity.com/integrations/crowdstrike/setup/pf_crowdstrike_ik_configuring_an_adapter_instance.html
revdate: June 10, 2024
section_ids:
  before-you-begin: Before you begin
  steps: Steps
  example: Example:
  result: Result:
  next-steps: Next steps
---

# Configuring an adapter instance

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

## Before you begin

Deploy the CrowdStrike Integration Kit files to your PingFederate directory.

## Steps

1. In the PingFederate administrative console, go to **Authentication > Integration > IdP Adapters** and 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 **CrowdStrike IdP Adapter**. Click **Next**.

3. On the **IdP Adapter** tab, in the **CrowdStrike Service API Response Mappings** section, map the attributes from the CrowdStrike Service API response to the attribute contract:

   1. Click **Add a new row to 'CrowdStrike Service API Response Mappings'**.

   2. In the **Local Attribute** field, enter a name for an attribute.

   3. In the **CrowdStrike Service API Response Mapping** field, enter the JSON Pointer syntax for the source Google Verified Access API attributes, as shown in [JSON Pointer syntax reference](pf_crowdstrike_ik_json_pointer_syntax_reference.html).

      ### Example:

      For example, the JSON pointer `/resource/0/system_serial_number` will return the system serial number.

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

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

      ### Result:

      These attributes are now available in your PingFederate authentication policy.

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

5. On the **Actions** tab, test your connection to the CrowdStrike service by fetching the API access token. Resolve any issues that are reported, and then click **Next**.

6. On the **Extended Contract** tab, add any attributes that you included in the **CrowdStrike Service API Response Mappings** section of the **IdP Adapter** tab. 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, review your configuration. Click **Save**.

## Next steps

Review [Using CrowdStrike Risk Level](pf_crowdstrike_ik_using_crowdstrike_risk_level.html).