Initiate the Authorize Endpoint for the Deployed External Client App with a Global Settings File

After the new org metadata is configured with its own global OAuth settings file, initiate an OAuth flow to acquire an access token.

1. Copy the consumerKey from the global OAuth settings file. This value only exists in the global OAuth settings file after you deploy and retrieve the External Client App OAuth settings.
2. Paste org 3’s URL and the consumer key into this URL in place of <org url> and <consumerKey>.

   <org url>/services/oauth2/authorize?response_type=code&client_id=<consumerKey>& redirect_uri=https://www.example.com

3. To initiate the request for access, open the URL in a browser.
4. Sign in with the new org’s credentials.
   You’re redirected, and an authorization code is included in the URL.
5. Copy the authorization code from the URL in the browser.
6. Decode the authorization code.
7. Copy the decoded authorization code.
8. Replace these values in the cURL request.
   • Replace <new org url> with the org’s URL.
   • Replace <authorization code> with the decoded authorization code from step 6.
   • Replace <clientKey> with the consumerKey field value from the global OAuth settings file.
   • Replace <clientSecret> with the consumerSecret field value from the global OAuth settings file.

   curl -X POST <new org url>/services/oauth2/token -d 'grant_type=authorization_code&code=<authorization code>&client_id=<clientKey>&client_secret=<clientSecret>&redirect_uri=https://www.example.com' | json_pp

9. Run the configured cUrl request in a terminal.
   A successful request returns an access token.
10. Verify that the access token works using Postman. Try accessing the UserInfo endpoint.