Deploying the provisioning connector
To get started with the integration, deploy the provisioning connector file from the PingOne Integration Kit to your PingFederate directory.
Steps
-
Download the PingOne Integration Kit
.zip
archive from the Add-ons tab of the PingFederate downloads page.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 Integration Kit files that you customized in
<pf_install>/pingfederate/server/default/conf/
includingpingfederate-messages.properties
. -
Delete the following files from
<pf_install>/pingfederate/server/default/deploy
:-
pf-pingone-datastore-<version>.jar
-
pf-pingone-pcv-<version>.jar
-
pf-p14c-datastore-<version>.jar
-
pf-p14c-pcv-<version>.jar
-
pf-pingone-quickconnection-<version>.jar
-
pf-p14c-quickconnection-<version>.jar
-
pf-pingoneuserstore-connector-<version>.jar
-
-
-
From the
.zip
archive, copy the contents ofdist
to<pf_install>/pingfederate/server/default/
. -
If you backed up any customized files, modify the new files with your customizations.
-
Merge the contents of
pingone-auth-messages.properties
into<pf_install>/pingfederate/server/default/conf/pingfederate-messages.properties
.-
If a key does not exist in
pingfederate-messages.properties
, add the line frompingone-auth-messages.properties
. -
If a key already exist in
pingfederate-messages.properties
, update it frompingone-auth-messages.properties
.
-
-
Enable the PingFederate provisioning engine.
-
In
<pf_install>/pingfederate/bin
, openrun.properties
for editing. -
Change
pf.provisioner.mode
toSTANDALONE
. Save the file.To configure the
FAILOVER
mode instead, see Deploying provisioning failover in the PingFederate documentation.Start PingFederate.
If you operate PingFederate in a cluster, repeat steps 2-6 and step 8 for each engine node.
-