---
title: "Changing Connected App Tokens"
description: "[Applies only to Veeam Backup for Salesforce versions prior to 3.2] Salesforce Connected App allows Veeam Backup for Salesforce to authenticate with Salesforce and get access to resources that will be protected."
canonical: "https://helpcenter.veeam.com/docs/backup_salesforce/userguide/connected_app.html"
breadcrumb: "User Guide > Configuring Veeam Backup for Salesforce > Configuring Security Settings > Changing Connected App Tokens"
dateModified: "2026-10-16"
---

# Changing Connected App Tokens

[Applies only to Veeam Backup for Salesforce versions prior to 3.2]

Salesforce Connected App allows Veeam Backup for Salesforce to authenticate with Salesforce and get access to resources that will be protected. You can create the Connected App in any Salesforce organization. To learn how to create the Connected App, see [this Veeam KB article](https://www.veeam.com/kb4240).

::: important

You can protect multiple Salesforce organizations using a single Veeam Backup for Salesforce installation. However, due to the Salesforce Connected App limit of 5 authorizations per client, authorization issues may occur when you have several product installations leveraging the same Connected App. That is why it is recommended that you create a dedicated Connected App for each product deployment. For more information on Salesforce OAuth Authorization Flows and Connected Apps, see [Salesforce Documentation](https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_flows.htm&type=5).

:::

During the [initial configuration](after_you_install.md), you are prompted to provide the Connected App OAuth tokens that are further used by Veeam Backup for Salesforce for the authentication process. However, you can change these tokens later in the Veeam Backup for Salesforce Web UI.

Keep in mind that if you change the Connected App tokens, you must also re-authorize all connections to Salesforce organizations added to Veeam Backup for Salesforce — otherwise, all backup and restore operations will fail. To re-authorize connections to Salesforce organizations, do either of the following:

- Navigate to **Configuration** > **Salesforce** > **Salesforce Orgs** and edit the connections as described in section [Editing Organizations](editing_connections.md).
- Navigate to the **Backup** tab and edit the related backup policies as described in section [Configuring Connection to Salesforce Organization](add_backup_policy_connect_salesforce.md).

## Changing Tokens

To change the OAuth tokens, do the following:

1. Switch to the **Configuration** page.
2. Navigate to **Security** > **Connected App**.
3. Click **Change Connected App Tokens**, and then click **Proceed** in the **Confirm Operation** window to acknowledge the operation.
4. Specify the type of the Salesforce organization where your Connected App is created.
5. Use the **Consumer key** and **Consumer secret** fields to provide the tokens obtained when creating the app.
6. Click **Connect**.

::: notes

If you have created a new Connected App, consider the following:

- The Connected App must be assigned the *Full access (full)* and *Perform requests at any time (refresh_token, offline_access)* OAuth scopes. For more information on OAuth scopes in Salesforce, see [Salesforce Documentation](https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_tokens_scopes.htm&type=5).
- If you have configured Salesforce as an identity provider in Veeam Backup for Salesforce, the *access unique user identifiers (openid)* OAuth scope must be granted to the new Connected App. Otherwise, you will not be able to change the Connected App tokens.
- The callback URL specified in the Connected App settings must match the Veeam Backup for Salesforce server address. You can copy the address in the **Setting up Salesforce Connected App** section.
- It takes up to 10 minutes for newly created OAuth tokens to become active.

:::

[![Changing Connected App Tokens](images/change_connected_app.png "Changing Connected App Tokens")](images/change_connected_app.png){.toggle scale=60}