Make sure you have completed the following tasks:

  1. Create an environment in PingOne. For more information, see Creating an environment.
  2. Create a custom risk policy in PingOne Risk. For more information, see Risk policies.
  3. Connect PingFederate to PingOne Risk. For more information, see Connecting PingFederate to PingOne.
  1. Download the PingOne Risk Integration Kit .zip archive from the Add-ons tab of the PingFederate downloads page.
  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 customized in <pf_install>/pingfederate/server/default/conf/.
    2. Delete pf-pingone-risk-management-adapter-<version>.jar from <pf_install>/pingfederate/server/default/deploy.

    If you are upgrading and not moving to 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/server/default/deploy 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.