Connect Salesforce DX to ECA
Give ECA governed access to Salesforce DX through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Salesforce DX to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Salesforce DX in Runlayer
Add Salesforce DX from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Install the Runlayer CLI so ECA can reach Salesforce DX, which runs on the user’s machine.
ECA setup guide - 3
Sign in to Salesforce DX
Sign in the way Salesforce DX requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Salesforce DX from ECA
Salesforce DX’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
Salesforce DX tools in ECA
Salesforce DX reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Salesforce DX call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more