---
title: Updating an existing deployment
description: If you're upgrading from a previous version of the SCIM Connector, note your existing service provider (SP) connection configuration and create a new connection.
component: code42-pingfederate
page_id: code42-pingfederate:updating_an_existing_deployment:pf_code42_integration_upgrading_an_existing_deployment
canonical_url: https://docs.pingidentity.com/integrations/code42-pingfederate/updating_an_existing_deployment/pf_code42_integration_upgrading_an_existing_deployment.html
revdate: June 26, 2024
section_ids:
  updating-an-existing-deployment-in-pingfederate-10-1-or-later: Updating an existing deployment in PingFederate 10.1 or later
  steps: Steps
  updating-an-existing-deployment-in-pingfederate-10-0-or-earlier: Updating an existing deployment in PingFederate 10.0 or earlier
  steps-2: Steps
---

# Updating an existing deployment

If you're upgrading from a previous version of the SCIM Connector, note your existing service provider (SP) connection configuration and create a new connection.

## Updating an existing deployment in PingFederate 10.1 or later

### Steps

1. Back up your current PingFederate configuration as shown in [Configuration archive](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_configurationarchivetasklet_selectimportexportstate.html) in the PingFederate documentation.

2. In the PingFederate administrative console, go to **Applications > Integration > SP Connections** and select your connection.

3. Note the attribute mappings for your existing SP connection.

   For help, see [Mapping attributes](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saasattrmappingmgmtstate.html) in the PingFederate documentation.

4. Delete your existing SP connection.

   1. Go to **Applications > Integration > SP Connections**.

   2. For your existing connection, click **Select action**, and then click **Delete**. Click **Confirm.**

5. Complete the steps in [Deploying the integration files](../pf_code42_integration_deploying_the_integration_files.html).

6. Complete the steps in [Creating a provisioning connection](../provisioning_setup/pf_code42_integration_creating_a_provisioning_connection.html).

   * From **Outbound Provisioning > Manage Channels > Channel**, on the **Attribute Mapping** tab, configure the attribute mappings based on your notes.

7. Complete the steps in [Creating a single sign-on connection](../single_sign-on_setup/pf_code42_integration_creating_a_single_sign_on_connection.html).

## Updating an existing deployment in PingFederate 10.0 or earlier

### Steps

1. Back up your current PingFederate configuration as shown in [Configuration archive](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_configurationarchivetasklet_selectimportexportstate.html) in the PingFederate documentation.

2. In the PingFederate administrative console, go to **Identity Provider > SP Connections** and select your connection.

3. Note the attribute mappings for your existing SP connection.

   For help, see [Mapping attributes](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saasattrmappingmgmtstate.html) in the PingFederate documentation.

4. Delete your existing SP connection.

   1. Go to **Identity Provider > SP Connections > Manage All**.

   2. For your existing connection, click **Select action**, and then click **Delete**. Click **Save.**

5. Complete the steps in [Deploying the integration files](../pf_code42_integration_deploying_the_integration_files.html).

6. Complete the steps in [Creating a provisioning connection](../provisioning_setup/pf_code42_integration_creating_a_provisioning_connection.html).

   * From **Outbound Provisioning > Manage Channels > Channel**, on the **Attribute Mapping** tab, configure the attribute mappings based on your notes.

7. Complete the steps in [Creating a single sign-on connection](../single_sign-on_setup/pf_code42_integration_creating_a_single_sign_on_connection.html).