Set Up the Subscriber Org with Browser Flow (Per-User Authentication)
This Page
All Documentation
Use this option when users in the subscriber org should see only records in the publisher org that they’re authorized to access. Each user completes a one-time browser login to the publisher org, and subsequent data requests run under their individual OAuth token. This authentication method is the right choice for regulated industries, compliance-sensitive data, or any scenario where a shared service account would create audit or access control issues.
Prerequisites: Set Up the Publisher Org
Before you set up the subscriber org, you must set up the publisher org. Follow the steps in Set Up the Publisher Org and be sure that the external client app has the right settings for browser flow authentication.
Step 1: Create an External Auth Identity Provider (XIDP) in the Subscriber Org
XIDP has been available since the Summer ’26 release and is the recommended auth provider method going forward. If your org uses auth providers, skip to Step 1 (Auth Provider Variant):
From the Quick Find box in Setup, enter Named Credentials, and select Named Credentials.
Click the External Auth Identity Providers tab and click New.
Enter a Label and a Name, for example, Acme_BrowserFlow_XIDP.
Enter these fields:
Authentication Protocol: OAuth 2.0
Flow Type: Authorization Code (Browser Flow).
Enter these values.
Client ID: the Consumer Key value you saved when you created the external client app in the publisher org.
Client Secret: the Consumer Secret value you saved when you created the external client app in the publisher org.
Select Use Proof Key for Code Exchange (PKCE) Extension. The external client app requires PKCE for browser flow, so without it authentication fails with a “missing required code challenge” error.
Click Save.
Copy the Callback URL from the saved XIDP.
Go back to the publisher org and open the external client app. On the Settings tab, under OAuth Settings, replace the placeholder Callback URL with the saved value.
Step 1: (Auth Provider Variant) Create an Auth Provider in the Subscriber Org
From the Quick Find box in Setup, enter Auth Providers, and select Auth Providers.
Click New.
For Provider Type, select Salesforce.
Set these fields:
Name: Acme_AuthProvider
Consumer Key: the Consumer Key value you saved when you created the external client app in the publisher org.
Consumer Secret: the Consumer Secret value you saved when you created the external client app in the publisher org.
Select Use Proof Key for Code Exchange (PKCE) Extension. The external client app requires PKCE for browser flow, so without it authentication fails with a “missing required code challenge” error.
Click Save. Copy the Callback URL from the saved auth provider.
Go back to the publisher org, and open the external client app. On the Settings tab, under OAuth Settings, replace the placeholder Callback URL with the saved value.
Step 2: Create the External Credential
From the Quick Find box in Setup, enter Named Credentials, and select Named Credentials.
From the External Credentials tab, click New.
Enter these fields:
Label: Acme_BrowserFlow_EC
Name: Acme_BrowserFlow_EC
For Authentication Protocol, select OAuth 2.0.
For Authentication Flow Type, select Browser Flow.
For Identity Provider, select the XIDP or auth provider you created in Step 1.
Click Save.
On the External Credential detail page, scroll to Principals and click New.
In the Parameter Name field, enter ClientCredsPrincipal.
For Identity Type, select Named Principal.
Click Save.
Step 3: Grant Credential Access Using a Permission Set
All users who will query the external objects need a permission set granting access to this external credential’s principal. If you skip this step, the Validate and Sync process fails with an “internal server error” that’s actually a permissions failure.
From the Quick Find box in Setup, enter Permission Sets, and select Permission Sets.
Click New.
Enter a label such as Acme_CrossOrg_BrowserFlow and click Save.
From the permission set page, click External Credential Principal Access.
Click Edit.
Enable your external credential’s principal Acme_BrowserFlow_EC - ClientCredsPrincipal and click Save.
Click Manage Assignments to assign this permission set to yourself and all users who will query external objects.
Step 4: Create the Named Credential
From the Quick Find box in Setup, enter, Named Credentials, and select Named Credentials.
Click New.
Enter these fields:
Label: Acme_CrossOrg_BF_NC.
Name: Acme_CrossOrg_BF_NC.
URL: the publisher org’s My Domain URL you previously saved.
External Credential: select the external credential you created, in this case, Acme_BrowserFlow_EC.
Select Generate Authorization Header.
Click Save.
Step 5: Authenticate Via a Browser
Sign in to the publisher org once so the named principal gets an OAuth token.
From the Quick Find box in Setup, enter Named Credentials, and select Named Credentials.
Click the External Credentials tab, then click the external credential you created in Step 2.
In the Principals section, find your named principal. From the dropdown menu on its row, select Authenticate.
In the browser window that opens, log in to the publisher org as a user with API access and read access to Order__c, then click Allow.
Back on the external credential page, confirm that the principal’s Authentication Status is Configured.
Step 6: Create the External Data Source
From the Quick Find box in Setup, enter External Data Sources, and select External Data Sources.
Click New External Data Source.
Enter these fields:
External Data Source: Orders_EDS.
Type: Salesforce Connect: Cross-Org.
Named Credential: select the named credential you just created, in this case, Acme_CrossOrg_BF_NC.
Enable Writable External Objects: optional, select this field if you need to create, edit, or delete records in the publisher org.
Click Save.
Step 7: Validate and Sync External Objects
On the External Data Source page, click Validate and Sync. Salesforce queries the publisher org’s schema and lists available objects.
Select the Order__c object.
Click Sync.
From the Quick Find box in Setup, enter External Objects, and select External Objects. Confirm that the Acme Order external object appears in the list. If you see the Acme Order external object here, the connection works.