PingOne

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.

  2. Create a custom risk policy in PingOne Risk. Learn more in Risk policies.

  3. Connect PingFederate to PingOne Risk. Learn more in Connecting PingFederate to PingOne.

Steps

  1. Download the PingOne Risk Integration Kit .zip archive from the Add-ons tab of the PingFederate downloads page or the Ping Identity Marketplace.

  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.