This is an updated and improved version of the Salesforce connector! If you’re setting up Salesforce with ConductorOne for the first time, you’re in the right place.

Availability

ConductorOne only integrates with the Salesforce editions with API access: Salesforce Enterprise, Unlimited, Developer, and Performance editions.

You cannot use this connector successfully with Group or Essentials editions, or with Professional edition without an API add-on.

Learn more about which Salesforce editions support API access in the Salesforce documentation.

Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Salesforce credentials

Each setup method requires you to pass in credentials generated in Salesforce. Gather these credentials before you move on.

The owner of a Salesforce user account with a profile that includes the API Enabled and View Setup and Configuration permissions must perform this task.

Enable API access for your Salesforce user

Before you begin, make sure that the Salesforce user who will set up the integration with ConductorOne has a profile that includes the API Enabled and View Setup and Configuration permissions.

To edit a profile so that it includes the API Enabled and View Setup and Configuration permissions:

1. Log into Salesforce as an Administrator.

2. Click the gear icon and select Setup.

3. Search for “profiles” and select Profiles from the search results.

4. In the User Profiles list, locate the user profile you want to add the permission to and click Edit.

5. Find the Administrative Permissions section of the page and click to select API Enabled and View Setup and Configuration.

6. Click Save.

Your user’s profile can now access Salesforce APIs.

Locate your Salesforce domain

1. Log into the Salesforce admin panel and copy the URL from your browser.

   

   ConductorOne integrates with domains that use one of the following Salesforce URL structures:

   • my.salesforce.com
   • sandbox.my.salesforce.com
   • test.salesforce.com
   • lightning.force.com
   • develop.lightning.force.com
   • sandbox.lightning.force.com

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Salesforce cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Salesforce credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for Salesforce v2 and click Add.

3. Choose how to set up the new Salesforce connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Select your method of authenticating to Salesforce and click either OAuth or Username and password.

   If you chose OAuth:

   1. In the Domain field, enter your Salesforce domain.

   2. Optional. Check the box to tell ConductorOne to use Salesforce usernames as the email addresses for your organization’s accounts. This option is especially helpful if your organization uses multiple service accounts that all share a noreply@salesforce.com email address.

   3. Click Login with OAuth.

   4. Log in and authorize ConductorOne with your Salesforce instance.

   5. You will then be redirected back to the Salesforce setup page in ConductorOne, where you’ll see an authorization message.

   6. Click Save.

   If you chose Username and password:

   1. Enter your Salesforce username and password in the top two fields.

   2. Enter your Salesforce security token in the Security token field. If trusted IP is configured on your user, entering this token is optional. If needed, refer to Reset Your Security Token in the Salesforce documentation.

   3. In the Domain field, enter your Salesforce domain.

   4. Optional. Check the box to tell ConductorOne to use Salesforce usernames as the email addresses for your organization’s accounts. This option is especially helpful if your organization uses multiple service accounts that all share a noreply@salesforce.com email address.

   5. Click Save.

8. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Salesforce connector is now pulling access data into ConductorOne.

Set up a Salesforce cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Salesforce and ConductorOne.

See the ConductorOne Salesforce v2 integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Salesforce self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Salesforce credentials generated by following the instructions above

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Salesforce connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Salesforce connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Salesforce connector deployment:

Secrets configuration

# baton-salesforce-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-salesforce-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Salesforce credentials
  BATON_INSTANCE_URL: <Salesforce domain>
  BATON_SALESFORCE_PASSWORD: <Password to the Salesforce account>
  BATON_SALESFORCE_USERNAME: <Username for the Salesforce account>
  BATON_SECURITY_TOKEN: <Salesforce security token (optional if trusted IP is configured)>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-salesforce.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-salesforce
  labels:
    app: baton-salesforce
spec:
  selector:
    matchLabels:
      app: baton-salesforce
  template:
    metadata:
      labels:
        app: baton-salesforce
        baton: true
        baton-app: salesforce
    spec:
      containers:
      - name: baton-salesforce
        image: ghcr.io/conductorone/baton-salesforce:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-salesforce-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-salesforce
   

2. Apply the secret configuration:

   kubectl -n baton-salesforce apply -f baton-salesforce-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-salesforce apply -f baton-salesforce.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-salesforce}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Salesforce connector to. Salesforce data should be found on the Entitlements and Accounts tabs.

That’s it! Your Salesforce connector is now pulling access data into ConductorOne.

Troubleshooting the Salesforce integration

When I try to log in with OAuth, I see a “This feature is not currently enabled for this user” error

Salesforce returns this error if the user who is logging in with OAuth does not have permission to access the Salesforce APIs:

{"code":2, "message":"error getting info from connectorClient: [simpleforce] Error. http code: 403 Error Message:  This feature is not currently enabled for this user. Error Code: FUNCTIONALITY_NOT_ENABLED"}

If you see this message, follow the instructions to Enable API access for your Salesforce user and then try logging in again.