This documentation applies to older versions of WSO2 ESB connectors. To find the documentation relevant to the version you are using, select the connector from the WSO2 Connector Store and click Documentation.

All docs This doc

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents


Importing the Salesforce Certificate

To use the Salesforce connector, add the  <salesforce.init>  element in your configuration before carrying out any other Salesforce operations.

Before you start configuring the Salesforce connector, make sure to import the Salesforce certificate to your ESB client keystore.

Follow the steps below to import the Salesforce certificate into the ESB client keystore:

  1. Export the certificate to the file system.

  2. Import the certificate into the ESB client keystore using the Management Console or by using the following command:

    Code Block
    keytool -importcert -file <certificate file> -keystore <ESB>/repository/resources/security/client-truststore.jks -alias "Salesforce"
  3. Restart the server and deploy the following Salesforce configuration:



Secure Vault is supported for encrypting passwords. See, Working with Passwords on integrating and using Secure Vault.


You can save the Salesforce connection configuration as a local entry and then easily reference it with the configKey attribute in your operations. For example, if you saved the above <salesforce.init> entry as a local entry named MySFConfig, you could reference it from an operation like getUserInfo as follows:


Code Block
<salesforce.getUserInformation configKey="MySFConfig"/>


The Salesforce connector operation examples use this convention to show how to specify the connection configuration for that operation. In all cases, the configKey attribute is optional if the connection to Salesforce has already been established and is required only if you need to specify a different connection from the current connection.