Because the settings file and global settings file are separate elements of external client apps, you can update the settings file and deploy it to another org without affecting the authorization settings.
Complete these steps to update the source org with changes that you make on org 3.
Note If the developer org has a namespace, remove references to the namespace from the
external client app name in the settings files before you deploy.
- Open the settings file on org 3, and add the full scope to the commaSeperatedOauthScopes
field.
<?xml version="1.0" encoding="UTF-8"?> <ExtlClntAppOauthSettings xmlns="http://soap.sforce.com/2006/04/metadata"> <externalClientApplication>myeca</externalClientApplication> <label>myecaset</label> <commaSeparatedOauthScopes>Basic, Web, RefreshToken, Full</commaSeparatedOauthScopes> </ExtlClntAppOauthSettings> - Deploy these changes to org 3.
sf project deploy start --manifest package.xml --target-org johndoe@example3.com - Retrieve the metadata files from org 3.
sf project retrieve start --manifest package.xml --target-org johndoe@example3.com - Deploy these same files to org 1.
sf project deploy start --manifest package.xml --target-org johndoe@example.com - Verify that the deployment succeeds. You see three files in the external client app.
- Header file
- Settings file
- Policies files
- Initiate the Authorize Endpoint to Verify the Updated Metadata
Verify that the scope matches the update from one org to another.