Deploy an External Client App That References the Source Org’s Global OAuth Settings File

Deploy an external client app on a new org, and have it reference the source org’s credentials. To configure this relationship, edit the OAuth link in the OAuth settings file and remove the reference to the global OAuth settings file in the package.xml manifest file of the new org.

1. Open the package.xml manifest file and remove the ExtlClntAppGlobalOauthSettings type.

   <?xml version="1.0" encoding="UTF-8"?>
   <Package xmlns="http://soap.sforce.com/2006/04/metadata">
       <types>
           <members>*</members>
           <name>ExternalClientApplication</name>
       </types>
       <types>
           <members>*</members>
           <name>ExtlClntAppOauthSettings</name>
       </types>
       <types>
           <members>*</members>
           <name>ExtlClntAppOauthConfigurablePolicies</name>
       </types>
       <version>58.0</version>
   </Package>

2. Verify that the OAuth link in the OAuth settings file has the same value in both org 1 and org 2: [Org1_ID]:[Org1_Consumer_ID]
3. Deploy the changes to org 2.

   sf project deploy start --manifest package.xml --target-org johndoe@example2.com

   When the deployment succeeds, only three files are in the external client app: a header file, a settings file, and a policies file.

• Initiate the Authorize Endpoint for the Linked Org
  After org 2 is configured to reference org 1’s global settings file, initiate an OAuth flow to acquire an access token.