You are here:
Disassociate an External Client App from the Source Org’s Global Settings File
When an external client app in one org relies on the global settings file in a source org, you can break the link between the two orgs and generate a unique global settings file for the org.
To disassociate the linked external client app in org 2 from its source org global settings in org 1, there are two options.
- Create a settings file, global settings file, and policies file in org 2, like you did in Configure the Salesforce DX project for a Local External Client Apps.
- Configure the files in org 2 to remove references to the source org, and then deploy the external client app in org 2.
Complete these steps to configure the files in org 2 and disassociate it from org 1.
- Delete OAuth settings file in org 2.
sf project delete source --source-dir force-app/main/default/extlClntAppOauthSettings --target-org johndoe@example2.com - Retrieve the metadata files from the source org.
sf project retrieve start --manifest package.xml --target-org johndoe@example.com - Remove the OAuth link from the settings file.
- Verify that all four external client app files are referenced in the package.xml file.
- Deploy the configured external client app metadata in org 2.
sf project deploy start --manifest package.xml --target-org johndoe@example2.com - Verify that the OAuth link exists in the settings file and is correct for org 2.
[Org2_ID]:[Org2_Consumer_ID]
- Initiate the Authorize Endpoint for a Disassociated External Client App
After the disassociated org metadata is configured with its own global settings file, initiate an OAuth flow to acquire an access token.
Did this article solve your issue?
Let us know so we can improve!
