This topic describes how to configure Salesforce for masking with the Delphix Continuous Compliance Engine using the CData Salesforce JDBC driver.
Install the Salesforce driver
From the Delphix Downloads site, go to Home > Delphix Product Releases > Continuous Compliance > Application Solutions > Salesforce > JDBC Drivers > CDATA > OEM. Download the Salesforce JDBC driver ZIP file and its corresponding CDATA license file. Use the driver version certified for your Continuous Compliance Engine release; consult the release notes or maintained compatibility matrix for that release instead of selecting the latest driver automatically.
-
In the Continuous Compliance Engine, go to Settings > JDBC Drivers and click + JDBC Driver.
-
Upload the certified driver ZIP file and the license file. Include the CData driver version in the driver description because the engine UI and logs do not expose the version.
-
Set Class Name to
cdata.jdbc.salesforce.SalesforceDriver.
Create the Salesforce connector
Before creating the connector, configure the application and environment in the Continuous Compliance Engine. Follow the Creating an extended connector procedure. For Salesforce, choose Database - Extended, select the Salesforce JDBC driver, and set the schema name to Salesforce. Use the CData JDBC Driver for Salesforce connection options reference for supported JDBC properties.
The CData driver supports Basic Authentication and OAuth 2.0. OAuth 2.0 is recommended when it aligns with your Salesforce security policies.
Basic authentication
For Basic Authentication, include the Salesforce security token in the JDBC URL. In CData driver version 24 and later, explicitly set AuthScheme=Basic.
jdbc:salesforce:AuthScheme=Basic;Logfile=/var/delphix/masking/logs/AppLogs/cdata.log;Verbosity=2;SecurityToken="";UseSandbox=True;SSLServerCert=*;UseBulkAPI=true;BulkAPIConcurrencyMode=Parallel;WaitForBulkResults=true;BulkAPIVersion=v2;
To obtain a Salesforce security token, sign in with the connector user, open the user settings, select Reset My Security Token, and use the token sent by Salesforce in the JDBC URL.
OAuth 2.0 authentication
Salesforce OAuth authentication requires a Connected App. Configure the Connected App with the callback URL, OAuth scopes, consumer key, consumer secret, token policies, and session settings required by your organization.
Configure the OAuth settings file
The CData Salesforce driver ZIP file contains cdata.jdbc.salesforce.jar. Run the JAR to open the CData connection-property window:
java -jar <path-to-cdata.jdbc.salesforce.jar>
Configure the following properties as required:
| Property | Value or guidance |
|---|---|
AuthScheme | OAuth |
UseSandbox | True for a Salesforce sandbox |
UseBulkAPI | True |
BulkAPIConcurrencyMode | Parallel, subject to Salesforce limits |
WaitForBulkResults | True |
BulkAPIVersion | v2 for CData driver version 24 and later |
InitiateOAuth | GETANDREFRESH for first-time authorization or reauthorization |
OAuthClientId | Connected App client ID |
OAuthClientSecret | Connected App client secret |
OAuthSettingsLocation | Full path and filename for the OAuth settings file |
CallbackURL | Confirm the callback URL with the Salesforce administrator |
Logfile | /var/delphix/masking/logs/AppLogs/cdata.log |
Use the CData connection window's copy function to copy the complete connection string. Manually copying visible fields can omit hidden parameters.
Upload the OAuth settings file
Test the OAuth connection and wait for the connection-success result.
Use the Continuous Compliance Engine API
POST /file-uploadsendpoint to upload the OAuth settings file.Set the
permanentquery parameter totrue.Copy the returned
fileReferenceIdand use it as theOAuthSettingsLocationvalue in the JDBC URL.Confirm that Salesforce objects appear in the Ruleset wizard.
OAuth refresh
Review the refresh-token policy for the Salesforce Connected App. If the refresh token expires, the Continuous Compliance Engine can lose access to Salesforce objects and masking jobs can fail.
CData log considerations
The CData log is written to the path configured in the JDBC URL and is included in engine support bundles. Verbosity level 3 or higher can capture sensitive data. Do not increase the verbosity unless the customer and Delphix Security approve the change.
Use the Rehearsal Tool for Salesforce metadata
For Continuous Compliance Engine version 2025.3.0.0 and later, Rehearsal Tool tasks are integrated into the masking job creation workflow. The integrated tasks can disable Salesforce metadata before masking and restore it afterward.
Supported metadata packages include triggers, workflows, Process Builders, validation rules, feeds, field history, duplicate rules, picklists, global picklists, unique settings, matching rules, required settings, and lookup filters.
For detailed task behavior and limitations, see Built-in CData Salesforce driver support plugin and the Rehearsal Tool documentation.
Salesforce masking performance
Salesforce Bulk API limits affect masking performance. Tune commit size and thread count together, and validate the configuration against the current Salesforce limits for the target organization.
A larger commit size can create larger batches.
More threads can increase parallel processing but can also increase locking and API-throttling risk.
Use serial processing or reduce concurrency when parent-child relationships cause locking conflicts.
Troubleshoot Salesforce masking
Parent-child relationships and row locks
Concurrent updates to related Salesforce records can cause UNABLE_TO_LOCK_ROW errors. Review parent-child and lookup relationships, avoid masking related objects concurrently, reduce commit size, or use serial Bulk API processing.
Field History
Field History can retain values copied during a Salesforce sandbox refresh. Review Field History settings before masking non-production data to reduce the risk of exposing pre-masked values.
Tables do not appear in the Ruleset wizard
Check the connector credentials and confirm that the JDBC URL includes UseSandbox=True when connecting to a Salesforce sandbox.
Verify data with Workbench
Use the Salesforce Workbench to run SOQL queries and verify masked records in the target Salesforce environment.