Common Errors on Salesforce OAuth
Overview
When connecting to Salesforce, there are several common OAuth errors you might encounter. This guide walks through the typical causes and provides step by step actions to resolve each one.
OAUTH_APPROVAL_ERROR_GENERIC An unexpected error has occurred during authentication
Cause:
Due to the following change, Salesforce Connected apps might need to be installed in an organization before OAuth authentication can be completed.
Resolution Steps:
When the initial user goes through the OAuth process, the app will be listed in the org and an admin will need to install the connected app.
Log in to Salesforce as a System Administrator.
Head to Setup.
Search for "Connected Apps OAuth Usage"
Find "Scrybe Salesforce for Jira" and click the Install button
Alternatively, you can also do the following:
If the above option is not feasible, a Salesforce Administrator can grant a permission to the user's profile.
Login as Salesforce Administrator and navigate to Setup.
In the Quick Find box, search for "Profiles" and open the user’s profile.
In the "System Permissions" section, they should enable the "Approve Uninstalled Connected Apps" permission.
After the Salesforce Administrator completes the steps above, ask your users to do the following before attempting to connect again: • Clear their browser cache and cookies • Retry connecting to Salesforce again
OAUTH_ERROR=TRUE
Ensure that the user’s profile in Salesforce includes the "API Enabled" permission. This permission is essential for API access within your organization. Without it, the user will not be able to connect their personal Salesforce account to send activities.
OAUTH_APP_BLOCKED
Verify that Scrybe Salesforce for Jira application is not blocked. If it is blocked, please unblock the app to restore access.
Additional Resources
If you need further assistance, don’t hesitate to contact our support team at [email protected]. We’re always happy to help!
Last updated