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:
-
Create an environment in PingOne. For more information, see Creating an environment.
-
Create a custom risk policy in PingOne Risk. For more information, see Risk policies.
-
Connect PingFederate to PingOne Risk. For more information, see Connecting PingFederate to PingOne.
Steps
-
Download the PingOne Risk Integration Kit
.zip
archive from the Ping Identity Integration Directory. -
Stop PingFederate.
-
If you are upgrading an existing deployment, back up your customizations and delete earlier versions of the integration files:
-
Back up any PingOne Risk Integration Kit files that you have customized in the
<pf_install>/pingfederate/server/default/conf/
directory. -
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.
-
-
Extract the
.zip
archive and merge the contents of thedist
directory with your<pf_install>/pingfederate
directory. -
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. -
If you backed up any customized files, modify the new files with your customizations.
-
Start PingFederate.
-
If you operate PingFederate in a cluster, repeat steps 2-7 for each engine node.