Troubleshooting SFDC OAuth connection errors

Troubleshooting SFDC OAuth connection errors

In September of 2025 there was a Salesforce policy change that altered the way token authorizations are granted from 3rd party apps. This could lead to errors end users have when trying to authorize their Salesforce token such as the one pictured below.  This doc will walk you through troubleshooting steps of how to resolve this issue:

IMPORTANT: After troubleshooting with the below steps please be sure to check the steps at the bottom of this doc to ensure that your integration user still has an active SFDC token.  Failing to check this could result in your SFDC <> Terret sync breaking entirely. 

First thing to check is that the Vocalo app has been installed.

Go to Salesforce Setup and search for Connected Apps OAuth Usage.  Once there, find the Vocalo App.  If it has not yet been installed, please install it.  If it has already been installed it would say ‘uninstall’ as one of the options and then you should be all set, see below.

 

Once you’ve confirmed that the app has been installed, search for Manage Connected Apps in the Salesforce setup.  Then find the Vocalo app and click edit. 

In the OAuth Policies section where it says Permitted Users, please change that setting to “Admin approved users are pre-authorized” and save. 

Next configuration to check is that you have a BoostUp permission set with the correct assigned connected apps and that it is assigned to your users.  

If you have already installed the BoostUp app you can navigate to the instructions below that walk through how to clone the existing BoostUp permission set and update the assigned connected apps.

If you do not have the BoostUp app installed and do not have the BoostUp Permission set created and assigned to your users, please follow these steps:

1. Navigate to the Salesforce Setup and search for Permission Sets in the quick find bar.  Once on the Permission Sets page, create a new permission set.  

2.  Once saved, in the permission set settings click on Assigned Connected Apps, then click edit, add the 'Vocalo' app and click save.  Once that is complete assign that permission set to your users.  

    

   

   

BoostUp Permission Set where BoostUp app is already installed

Go to permission sets in SFDC setup and find the “BoostUp Users clone” Permission set.

In the “BoostUp Users Clone” permission set, click on Assigned Connected Apps, then click edit, add the 'Vocalo' app and click save.  Once that is complete assign that permission set to your users. 

IMPORTANT:  After completing the troubleshooting steps above, you'll want to check to make sure your integration user still has an active OAuth token with SFDC as changing connected app settings can result in integration user token expiration.  

1.  To check this, please login to Terret as your integration user and click on the settings cog in the bottom left corner. 

2. On the link accounts page you land on, please click on the 'Test Account Link' button right below 'Authorize Salesforce Account' (this may also say 'Retest Account Link' under 'Re-authorize Salesforce Account').  If you get a green message saying "Salesforce Service Working Properly", then you're all set.  If you receive a message saying 'Salesforce Service not working', then please follow the below steps to re-authorize your OAuth Token for the integration user.

   

3. Click Link Salesforce Account and you'll be redirected to a pop up page with an SFDC login prompt.  Please complete the login prompt with the login credentials of the SFDC user that you'd like to use as the integration user of Terret.  The pop up page may ask you to "Allow" permissions for certain things, please click allow.  Once you complete the prompts in the pop up page, you should be redirected back to the Link Accounts page you started on.  Please test the account link again to make sure you get a green message saying "Salesforce Service Working Properly".  If you completed these steps, please reach out to support@terret.ai to let them know you've just re-established an OAuth token for the integration user and to check and make sure the sync is working properly.