---
title: Deploying the integration files
description: To get started with the integration, deploy the PingOne Risk Integration Kit files to your PingFederate directory.
component: pingone
page_id: pingone:pingone_risk_integration_kit:pf_p1_risk_ik_deploying_the_integration_files
canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_risk_integration_kit/pf_p1_risk_ik_deploying_the_integration_files.html
revdate: July 10, 2024
section_ids:
  before-you-begin: Before you begin
  steps: Steps
---

# Deploying the integration files

To get started with the integration, deploy the PingOne Risk Integration Kit files to your PingFederate directory.

## Before you begin

Make sure you have completed the following tasks:

1. Create an environment in PingOne. Learn more in [Adding an environment](https://docs.pingidentity.com/pingone/pingone_tutorials/p1_tutorial_passwordless_create_environment.html).

2. Create a custom risk policy in PingOne Risk. Learn more in [Risk policies](https://docs.pingidentity.com/pingone/threat_protection_using_pingone_protect/p1_protect_risk_policies.html).

3. Connect PingFederate to PingOne Risk. Learn more in [Connecting PingFederate to PingOne](pf_p1_risk_ik_connecting_pf_to_p1.html).

## Steps

1. Download the PingOne Risk Integration Kit `.zip` archive from the [**Add-ons** tab of the PingFederate downloads page](https://www.pingidentity.com/en/resources/downloads/pingfederate.html) or the [Ping Identity Marketplace](https://marketplace.pingone.com/item/pingone-risk-integration-kit).

2. Stop PingFederate.

3. If you are upgrading an existing deployment, back up your customizations and delete earlier versions of the integration files:

   1. Back up any PingOne Risk Integration Kit files that you have customized in the `<pf_install>/pingfederate/server/default/conf/` directory.

   2. Delete the `pf-pingone-risk-management-adapter-<version>.jar` file from the `<pf_install>/pingfederate/server/default/deploy` directory.

      |   |                                                                                                         |
      | - | ------------------------------------------------------------------------------------------------------- |
      |   | If you are upgrading and not moving to the Signals SDK, you must update the template HTML and JS files. |

4. Extract the `.zip` archive and merge the contents of the `dist` directory with your `<pf_install>/pingfederate` directory.

5. If there is more than one version of the `pf-authn-api-sdk-<version>.jar` file in your `<pf_install>/pingfederate/server/default/lib` directory, delete all but the latest version of the file.

6. If you backed up any customized files, modify the new files with your customizations.

7. Start PingFederate.

8. If you operate PingFederate in a cluster, repeat steps 2-7 for each engine node.