---
schema_version: "1"
id: 7f360d8feba4eb7219879a974a27b71e37244ba11c3757e0f745e286eb7ce0a2
title: Salesforce Data Cloud Connector 1.4 - Additional Configuration Information
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/salesforce-data-cloud-connector/1.4/salesforce-data-cloud-connector-config-topics.md
canonical_url: https://docs.mulesoft.com/salesforce-data-cloud-connector/1.4/salesforce-data-cloud-connector-config-topics
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 0ec7a12e5b0501788b39d1c3ccf0188d6d778679608a30c53ce12b067aa5053f
description: MuleSoft Documentation Site
release: "1.4"
latest: false
---
---
product: Salesforce Data Cloud Connector
version: 1.4
---

# Salesforce Data Cloud Connector 1.4 - Additional Configuration Information

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Configure Anypoint Connector for Salesforce Data Cloud (Salesforce Data Cloud Connector) to generate
an OAuth 2.0 keystore file.

## Generate a Keystore File

Salesforce Data Cloud Connector uses the Bouncy Castle cryptographic library to load the certificate
from the keystore and sign the payload for the authentication requests.

The Bouncy Castle library has a
[vulnerability (CVE-2018-5382)](https://nvd.nist.gov/vuln/detail/CVE-2018-5382) that relates to the
BKS-V1 keystore file type, so do not use BKS-V1 keystore files, as documented in the
[Bouncy Castle proposed solution](https://www.kb.cert.org/vuls/id/306792). By default, Salesforce
Data Cloud Connector uses JKS or PKCS12 keystores.

To generate a JKS keystore file:

1.  Go to your Mule workspace and open the terminal or shell application for your operating system.

2.  Enter this command:

    ```none
    keytool -genkeypair -alias salesforce-cert -keyalg RSA -keystore salesforce-cert.jks
    ```

3.  Enter the following information:

    - Password for the keystore

    - Your first name and last name

    - Your organization unit

    - Your city and state, and the two-letter code for your country

      The system generates a Java keystore file (JKS format) that contains a private or public key
      pair in your workspace.

4.  Provide the file path for the keystore in your connector configuration.

    Enter this command:

    ```none
    keytool -exportcert -alias salesforce-cert -file salesforce-cert.crt -keystore salesforce-cert.jks
    ```

    The system exports the public key from the keystore into the workspace. This is the public key
    to enter in your Salesforce instance.

5.  Verify that you have both the keystore (`salesforce-cert.jks`) and the public key
    (`salesforce-cert.crt`) files in your workspace.

## Next Step

After you complete configuring the connector, you can try the
[Examples](https://docs.mulesoft.com/salesforce-data-cloud-connector/1.4/salesforce-data-cloud-connector-examples).

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Salesforce Help](https://help.salesforce.com)