Connect Multiple Salesforce Orgs in Secure

Secure enables you to connect multiple Salesforce orgs for reporting purposes in the Connections section on the Settings tab.

Supported connections include one production org and its associated sandboxes or multiple production orgs. Sandbox orgs are only available for setup as children in a connection. A production org can be setup as the parent of a connection or a child.

A production org can't be a parent in one connection while being a child in another.

Before connecting multiple Salesforce orgs, determine which org is the parent and which orgs are the children. When connecting a production org and its associated sandboxes, the production org defaults as the parent. When connecting multiple production orgs, only the parent can report on key statistics for the entire connection. Deploy a connected app in the children and a named credential in the parent.

Note Users configuring connections must have System Administrator access to both the parent and child orgs.

Complete the process for each user that requires reports on key security statistics within multiple orgs.

1. Obtain the My Domain URLs for both the parent and children orgs being connected.
   1. Go to Salesforce Setup, navigate to Company Settings, click My Domain, and copy My Domain URL.
   2. Add "https://" to the beginning of the URL and ensure there are no trailing slashes.
2. In the child org, navigate to the Settings tab in Secure, select Connections, and click Setup as Child Org.
   To connect the child org to the parent, a Connected Application needs to be created and deployed in the child org. The Alias is used to identify the org. Use a single word or short phrase that is recognized within the user’s organization. The alias can only contain alphanumeric characters and numbers. It must begin with a letter, not end with a space or underscore, and not contain two consecutive spaces or underscores. The Alias has a character limit of 24. It is used to match the child to the parent. Note what you enter for future reference.
3. The Instance URL is the My Domain URL of the parent, which was obtained in Step 1. Add the "https://" and ensure there are no trailing slashes or spaces after the URL.
4. After the Alias and Instance URL are entered, click Deploy.
   The “Deploy Connected Application” window refreshes and provides a link to go directly to the Connected App in the Salesforce Setup menu.
5. Click the "link".
6. On the Manage Connected Apps page, in the "API (Enable OAuth Settings)" section, a Consumer Key and Consumer Secret are available. Copy them for use in connecting the child org to the parent. By default, the Consumer Secret is hidden, so the user needs to select the “Click to reveal” link for the Consumer Secret to be displayed.
7. In the parent org, navigate to the Settings tab in Secure, then Connections, and click Authorize New Salesforce Org.
8. To connect the child org to the parent, create and deploy a Named Credential within the parent org.
   1. The Alias is used to identify the org. Enter it exactly as it was entered in the child org in Step 2-1.
   2. Copy and paste the Consumer Key from the child org.
   3. Copy and paste the Consumer Secret from the child org.
   4. The Instance URL is the My Domain URL of the child, which was obtained in Step 1. Add "https://" and ensure there are no trailing slashes after the URL.
   A description may be entered and is displayed in the parent org. This helps to further identify the org.
9. Click Deploy.
   The Deploy Named Credential window refreshes and provides a link to go directly to the Named Credential in the Salesforce Setup menu.
10. Click the "link".
    The user is automatically taken to the Authentication Settings for External Systems page for the Named Credential.
11. Click Save on the Authentication Settings for External Systems.
    The user is presented with the login screen for the child org.
12. Login using the child org’s credentials.
13. You must allow access for the connection to complete. Click Allow.
    The connection is setup. These same steps need to be completed for each child org and each user who wants to report on key security statistics in multiple orgs.