When you configure a connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials the connector uses to access the target Salesforce system.
You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your authorization credentials in the global configuration properties. For information about the benefits of using property placeholders and how to configure them, see Anypoint Connector Configuration.
To configure a global element for Salesforce Connector, follow these steps:
Select the name of the connector in the Studio canvas.
In the configuration screen for the operation, click the plus sign (+) next to the Connector configuration field to access the global element configuration fields.
In the General tab, select one of these authentication methods for your connection:
Basic authentication
OAuth 2.0 authentication
OAuth JWT authentication
OAuth SAML authentication
OAuth Username Password authentication
In the Apex tab, optionally configure Apex Settings.
In the Advanced tab, optionally specify reconnection information, including a reconnection strategy.
Click Test Connection to confirm that Mule can connect with the specified server.
Click OK.
Authentication
For all OAuth connections, you can specify an object store that stores each resource owner’s ID data. If you don’t specify an object store, Mule automatically provisions the default object store. The app interacts with the object store automatically when a new resource owner is authenticated, the access token is refreshed, or the access token is invalidated.
All authentication types support mutual TLS. To use mutual TLS, you need a keystore file and a password for the file. See Generate a Keystore File for more information.
In Studio, when you configure the connector’s authentication method, specify the path to the keystore file and the TLS password on the Security tab.
To set up a mutual TLS certificate in your Salesforce environment, see Set Up a Mutual Authentication Certificate.
Basic Authentication
Basic authentication uses a username and password for authentication.
Important fields in the General tab include the following:
| Field | Description |
|---|---|
Username | Salesforce username. |
Password | Corresponding password. |
Security token | Corresponding security token. |
Callback path | Path for the callback, for example, |
Authorization URL | Web service URL responsible for user authentication. This is the URL for the endpoint configured to handle SOAP authentication requests. It defaults to the URL that contains the latest API version supported by the connector, for example, |
OAuth 2.0 Authentication
Use OAuth 2.0 to delegate user authentication to the service hosting the user account. For more information, refer to Configuring OAuth 2.0 for Connectors or Configuring OAuth 2.0 for Connectors on CloudHub.
OAuth 2.0 delegates user authentication to the service hosting the user account.
Important fields in the General tab include the following:
| Field | Description |
|---|---|
Consumer key | Consumer key for the Salesforce-connected app. See the Salesforce documentation for information about generating a consumer key. |
Consumer secret | Password for the keystore. |
Listener config | Configuration for the listener, for example, `HTTP_Listener_config. |
Callback path | Path for the callback, for example, |
Authorize path | Path for authorization, for example, |
External call back url | Callback URL, for example, |
Important fields in the Advanced tab include the following:
| Field | Description |
|---|---|
Api version | API version used. Defaults to the latest API version supported by the connector. |
OAuth JWT Authentication
OAuth JWT uses OAuth 2.0 with a JSON Web Token (JWT) request for user authentication.
Important fields in the General tab include the following:
| Field | Description |
|---|---|
Consumer key | Consumer key for the Salesforce-connected app. See the Salesforce documentation for information about generating a consumer key. |
Key store | Path to the keystore that signs data during authentication. See Generate a Keystore File. |
Store password | Password for the keystore. |
Password | Corresponding password. |
Certificate Alias | Alias of the certificate to use if the specified keystore contains multiple certificates. |
Principal | Username of the Salesforce user. |
Important fields in the Advanced tab include the following:
| Field | Description |
|---|---|
Api version | API version used. Defaults to the latest API version supported by the connector. |
OAuth SAML Authentication
| OAuth SAML currently uses only Salesforce as an identity provider. Refer to Salesforce as a SAML Identity Provider to enable Salesforce as an identity provider. |
OAuth SAML uses OAuth 2.0 with a signed SAML 2.0 assertion to request an access token.
Important fields in the General tab include the following:
| Field | Description |
|---|---|
Consumer key | Consumer key for the Salesforce-connected app. See the Salesforce documentation for information about generating a consumer key. |
Key store | Path to the keystore that signs data during authentication. See Generate a Keystore File. |
Store password | Password for the keystore. |
Password | Corresponding password. |
Certificate Alias | Alias of the certificate to use if the specified keystore contains multiple certificates. |
Principal | Username of the Salesforce user. |
Important fields in the Advanced tab include the following:
| Field | Description |
|---|---|
Api version | API version used. Defaults to the latest API version supported by the connector. |
OAuth Username Password Authentication
OAuth Username Password authentication uses OAuth 2.0 with a user and password for authentication.
Important fields in the General tab include the following:
| Field | Description |
|---|---|
Consumer key | Consumer key for the Salesforce-connected app. See the Salesforce documentation for information about generating a consumer key. |
Consumer secret | Consumer secret for the connector to access Salesforce. |
Username | Salesforce username. |
Password | Corresponding password. |
Security token | Corresponding security token. |
Important fields in the Advanced tab include the following:
| Field | Description |
|---|---|
Api version | API version used. Defaults to the latest API version supported by the connector. |
Apex Settings
Salesforce Connector gets the names of the Apex classes and the associated methods that can be invoked when you connect to Salesforce.
To configure Apex settings in Studio:
Click the Apex tab in the global element properties screen.
Enter the following information:
Field Description Fetch All Apex SOAP Metadata
Fetches the metadata of all the Apex SOAP classes. Takes precedence over Apex Class Name settings.
Fetch All Apex REST Metadata
Fetches the metadata of all the Apex REST classes. Takes precedence over Apex Class Name settings.
Apex Class Names
List of Apex class names to use for limiting the set of classes you fetch and the methods that they expose. This setting can accelerate the fetch process if you don’t need to fetch many classes. Valid values:
None
No classes are specified for DataSense to acquire.
From a message
Enables you to specify the class name using an expression.
Create object manually
Enables you to create a list of class names for DataSense to acquire. DataSense acquires only those classes and their associated methods.
