---
title: Deploying the provisioning connector
description: To get started with the integration, deploy the provisioning connector file from the PingOne Integration Kit to your PingFederate directory.
component: pingone
page_id: pingone:pingone_integration_kit:pf_p1_ik_deploying_the_provisioning_connector
canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_integration_kit/pf_p1_ik_deploying_the_provisioning_connector.html
revdate: June 18, 2024
section_ids:
  steps: Steps
---

# 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

1. Download the PingOne 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-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 Integration Kit files that you customized in `<pf_install>/pingfederate/server/default/conf/` including `pingfederate-messages.properties`.

   2. 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`

4. From the `.zip` archive, copy the contents of `dist` to `<pf_install>/pingfederate/server/default/`.

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

6. Merge the contents of `pingone-auth-messages.properties` into `<pf_install>/pingfederate/server/default/conf/pingfederate-messages.properties`.

   1. If a key does not exist in `pingfederate-messages.properties`, add the line from `pingone-auth-messages.properties`.

   2. If a key already exist in `pingfederate-messages.properties`, update it from `pingone-auth-messages.properties`.

7. Enable the PingFederate provisioning engine.

   1. In `<pf_install>/pingfederate/bin`, open `run.properties` for editing.

   2. Change `pf.provisioner.mode` to `STANDALONE`.

      |   |                                                                                                                                                                                                                              |
      | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | To configure the `FAILOVER` mode instead, see [Deploying provisioning failover](https://docs.pingidentity.com/pingfederate/latest/server_clustering_guide/pf_deploy_provis_failover.html) in the PingFederate documentation. |

   3. Save the file.

8. Start PingFederate.

9. If you operate PingFederate in a cluster, repeat steps 2-6 and step 8 for each engine node.