Connections > Salesforce Mass Ingestion connection properties
  

Salesforce Mass Ingestion connection properties

When you set up a Salesforce Mass Ingestion connection, you must configure the connection properties.
The Salesforce Mass Ingestion connection uses a connected app to access the Salesforce data. Before you configure the connection, you must configure a connected app in Salesforce to allow the connection to access the Salesforce data.
Note: For more information about configuring a connected app, see the Knowledge Base article 000172095.
The properties of a Salesforce Mass Ingestion connection vary based on the authentication method that you specify for the connection. When you create a connection, you can select one of the following authentication methods:

Connection properties for OAuth 2.0 Username-Password Flow authentication

The following table describes the connection properties for a Salesforce Mass Ingestion connection configured with OAuth 2.0 Username-Password Flow authentication:
Connection property
Description
Connection Name
A name for the connection. This name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -
Spaces at the beginning or end of the name are trimmed and are not saved as part of the name. Maximum length is 100 characters. Connection names are not case sensitive.
Description
An optional description for the connection. Maximum length is 255 characters.
Type
The type of connection. For an Oracle Database Ingestion connection, the type must be Salesforce Mass Ingestion.
Runtime Environment
Name of the runtime environment where you want to run the ingestion tasks.
You must specify a Secure Agent as the runtime environment.
Note: You cannot run application ingestion tasks on a Hosted Agent or serverless runtime environment.
User Name
User name of the Salesforce account.
Password
Password for the Salesforce account.
Security Token
Security token associated with the Salesforce account.
You can configure the connection without specifying the security token if there are no IP restrictions specified for the connected app. However, you must specify the security token if IP restrictions are enforced for the connected app and if the Secure Agent is not running on the trusted IP range specified for your Salesforce organization.
Note: If you do not have the security token, reset the security token in Salesforce. For more information about resetting the security token, see the Salesforce documentation.
Consumer Key
Consumer key that Salesforce generates when you enable OAuth 2.0 authentication for the connected app.
Consumer Secret
Consumer secret that Salesforce generates when you enable OAuth 2.0 authentication for the connected app.
API Version
Version of the Salesforce API that you want to use to access the source data.
Default is 51.0.
Note: You cannot use a version older than 51.0.
OAuth token URL
OAuth 2.0 token endpoint of the Salesforce organization. The connected app sends access token requests to this endpoint.
Default value is:
https://login.salesforce.com/services/oauth2/token
This default URL is used for all Salesforce instances.
Alternatively, you can enter an instance-specific URL:
https://<instance domain URL>/services/oauth2/token
An instance-specific URL can establish a more direct and faster connection to the Salesforce host server. If the load on the common default endpoint is heavy and ingestion jobs fail with an authentication error when using it, use this alternative URL instead.
Note: For more information about the OAuth 2.0 Username-Password Flow authentication method, see the Salesforce documentation.

Connection properties for OAuth 2.0 JWT Bearer Flow authentication

The following table describes the connection properties for a Salesforce Mass Ingestion connection configured with OAuth 2.0 JWT Bearer Flow authentication:
Connection property
Description
Connection Name
A name for the connection. This name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -
Spaces at the beginning or end of the name are trimmed and are not saved as part of the name. Maximum length is 100 characters. Connection names are not case sensitive.
Description
An optional description for the connection. Maximum length is 255 characters.
Type
The type of connection. For an Oracle Database Ingestion connection, the type must be Salesforce Mass Ingestion.
Runtime Environment
Name of the runtime environment where you want to run the ingestion tasks.
You must specify a Secure Agent as the runtime environment.
Note: You cannot run application ingestion tasks on a Hosted Agent or serverless runtime environment.
User Name
User name of the Salesforce account.
Consumer Key
Consumer key that Salesforce generates when you enable OAuth 2.0 authentication for the connected app.
Keystore Path
Absolute path to the keystore file that contains the X509 certificate required to validate a JSON Web Token (JWT) and establish a secure connection with Salesforce.
The keystore file must be in the Java KeyStore (JKS) format.
Keystore Password
Password for the keystore file.
Private Key Alias
Alias name of the private key used to sign the JWT.
Private Key Password
Password for the private key.
API Version
Version of the Salesforce API that you want to use to access the source data.
Default is 51.0.
Note: You cannot use a version older than 51.0.
OAuth token URL
OAuth 2.0 token endpoint of the Salesforce organization. The connected app sends access token requests to this endpoint.
Default value is:
https://login.salesforce.com/services/oauth2/token
This default URL is used for all Salesforce instances.
Alternatively, you can enter an instance-specific URL:
https://<instance domain URL>/services/oauth2/token
An instance-specific URL can establish a more direct and faster connection to the Salesforce host server. If the load on the common default endpoint is heavy and ingestion jobs fail with an authentication error when using it, use this alternative URL instead.
Note: For more information about the OAuth 2.0 JWT Bearer Flow authentication method, see the Salesforce documentation.