Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

AutoRABIT Vault: Salesforce ECA (Local) Connection Setup Steps

This is a step by step on how to implement the Local ECA solution to establish a new connection with AutoRABIT Vault.

Pre-req: get your Callback URL (redirect URI)

For AutoRABIT’s Vault ECA setup, you need the callback URL

Callback URL is depending on the instance:

{$isntancename}/dashboard/setup/addSfOrg

Example:

https://vault-qa.autorabit.com/dashboard/setup/addSfOrg
1

Create the External Client App (ECA) in your Salesforce Org

  1. Login into Salesforce

  1. In Salesforce, go to Setup.

  2. In Quick Find, search External Client Apps.

  3. Open External Client App Manager (or the External Client Apps area).

  1. Click New External Client App.

  2. Fill in the basics:

  • Name / Label ( e.g. AR_Local)

  • API Name (auto-filled)

  • Contact Email

  • Distribution State:

    • Local (only for this org)

2

Important Note: After creating the ECA in Salesforce, there may be a replication delay on the Salesforce side. If you encounter the error error=invalid_client_id&error_description=client%20identifier%20invalid while attempting to connect or register the org, please wait 30 minutes, then try again to allow the Salesforce configuration to sync completely.

3

Enable OAuth + set callback URL + scopes

  1. Click Enable OAuth (or expand API (Enable OAuth Settings) and check Enable OAuth).

  2. Set *Callback URL

    The URL you collected in step 1.

  3. Choose OAuth Scopes:

    1. Access the Identity URL service (id, profile, email, address, phone)

    2. Manage user data via APIs

    3. Manage user data via web browsers (web)

    4. Full access (full)

    5. Perform requests at any time (refresh_token, offline_access.

4

Turnment

  1. In Flow Enablement, select Enable Authorization Code and Credentials Flow.

  2. user credentials are required in the POST body (Salesforce shows this option when you choose that flow) should be disabled.

5

Security toggles (common defaults)

In the Security section the next options should be enabled:

  • Require secret for Web Server Flow

  • Require secret for Refresh Token Flow

6

Create the app and capture Client ID / Secret

  1. Click Create.

  2. Open the app’s Settings tab and locate Consumer Key and Secret:

  • Consumer Key = Client ID

  • Consumer Secret = Client Secret

When you click the button for Consumer Key and Secret a code will be sent to the registered email for the user creating the configuration

After getting the code and verify in Salesforce the Consumer Key (CliendID) and Consumer Secret (Client Secret) will be displayed.

IMPORTANT: STORE THIS VALUE IN A SAFE PLACE WHERE IT CAN BE EASILY USED FOR FUTURE REFERENCE.

7

Configure Policies (very important)

After creating the ECA, open the Policies tab and adjust as needed (exact options vary by org/security posture), commonly:

  • Permitted Users: often set to Admin approved users are pre-authorized for controlled rollouts.

  • Add the required profiles/permission sets (or approved users) for whom is allowed to authorize.

8

What you’ll use in AutoRABIT

Once created, the set of values you’ll reference in your AutoRABIT Vault configuration are:

  • Client ID

  • Client Secret

Also, the internal direction is to be clear that one ECA per customer org can be used across products (rather than creating one per AR product).

After the configuration in Salesforce is complete, and you have obtained the ClientID and Client Secret, we can go to Vault to create the connection

In the menu Click Salesforce Org Integration

Create the connections, filling in the required information.

Enter the Client ID and Client Secret that you received from Salesforce.

Once the continue button is clicked, a Salesforce login is shown for the user we intend to use with the connection.

A message from Salesforce will show to require granted permissions for the user to use the scopes defined in the ECA, Click Allow.

Then you will be returned, and the connection will be saved.

Click finish, and the success message will appear.

Important: This setup is Salesforce org-specific. You must repeat this process for each customer Salesforce org you want to connect, since the External Client App is created inside (and scoped to) that org and produces org-specific credentials.

PreviousGuard: Salesforce ECA (Local) Connection Setup StepsNextARM FAQs

Last updated

Was this helpful?