Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.
Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Ingestion and Replication
  • All Products

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Back Next

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.
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:
  • OAuth 2.0 Username-Password Flow
    : Authenticates the connection by using the Salesforce account login credentials and the consumer key and consumer secret that Salesforce generates for the connected app.
  • OAuth 2.0 JWT Bearer Flow
    : Authenticates the connection by using the Salesforce account user name, private key alias, private key password, and the consumer key that Salesforce generates for the connected app. Informatica recommends that you use this authentication method because this method provides secured access to Salesforce without sharing sensitive information, such as consumer secret and Salesforce account password.

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
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.
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.
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.
Base URI
URL of the Salesforce organization.
You must enter the base URI in the following format:
https://<salesforce_org>.salesforce.com
OAuth token URL
OAuth 2.0 token endpoint of the Salesforce organization. The connected app sends the access token requests to this endpoint.
Default value is:
https://login.salesforce.com/services/oauth2/token
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
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.
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.
Base URI
URL of the Salesforce organization.
You must enter the base URI in the following format:
https://<salesforce_org>.salesforce.com
OAuth token URL
OAuth 2.0 token endpoint of the Salesforce organization. The connected app sends the access token requests to this endpoint.
Default value is:
https://login.salesforce.com/services/oauth2/token
For more information about the OAuth 2.0 JWT Bearer Flow authentication method, see the Salesforce documentation.
0 COMMENTS
We’d like to hear from you!