Salesforce has replaced connected apps with external client apps as the supported authentication model for API integrations. See Create an external client app for why migration matters and when it becomes required. Use this article to migrate an existing connection from a connected app to an external client app.
Note
Once you disconnect the legacy connected app, you cannot fall back to it. All new or re-established connections must use the external client app.
Before you begin
Check your current connection type in Fullcast: Navigate to Settings > Export-Import. If under Connections > Type it shows as Salesforce, you cannot migrate it yourself — file a request with Fullcast support to convert it to the current connection type, then continue with this article.
Confirm the Fullcast integration user exists and has the correct permission sets.
Confirm your Salesforce org allows the integration user to complete an interactive OAuth handshake. If your org enforces SSO, the integration user must either:
Be provisioned in your Identity Provider (Okta, Azure AD, or equivalent), or
Be assigned to a Salesforce profile where Is Single Sign-On Enabled is unchecked.
Contact your Salesforce administrator if you are unsure.
Check the Disable login with Salesforce credentials setting in your Salesforce org under Setup > Single Sign-On Settings. If this setting is enabled and your integration user is not provisioned in your Identity Provider, the OAuth handshake will fail during the external client app connection step.
Schedule a maintenance window. Data syncs will pause between disconnecting the connected app and completing the external client app setup.
Create the external client app in Salesforce
Create a new external client app in Salesforce for Fullcast. This app replaces the legacy connected app and provides the consumer key and consumer secret you will use in the next section.
Follow the steps in Create an external client app to complete the OAuth settings and policies in Salesforce.
Note
Keep the Consumer Key and Consumer Secret available. You will paste them into Fullcast in the next section.
Connect Fullcast to the new external client app
After the external client app is created in Salesforce, disconnect the legacy connected app in Fullcast and authenticate the new external client app. For the full step-by-step authorization flow, see Connect Fullcast to Salesforce with external client app.
Verify the migration
Confirm the new external client app connection is working before you remove the legacy connected app.
In Fullcast, go to Settings > Export-Import and confirm the connection status shows as connected.
Run a small test import job and confirm the job completes successfully.
Confirm data is flowing between Salesforce and Fullcast as expected.
In Salesforce, go to Setup > Users > Login History and confirm the integration user's most recent logins are authenticated through the external client app.
Optional. Remove the legacy connected app
Once the external client app is confirmed working and data syncs have resumed successfully, you can remove the legacy connected app from Salesforce.
In Salesforce, go to Setup > Apps > App Manager.
Locate the Fullcast connected app in the list.
From the row's action menu, select Delete and confirm.
Troubleshooting
If the browser authorization fails with a redirect loop or a 500 error, the most likely cause is an SSO policy blocking the integration user. Verify the SSO checklist in the Before you begin section. If the issue persists, contact your CSM.