How to Configure OAuth Authentication for Salesforce in ZappySys (Avoid Legacy SOAP login())

SSIS PowerPack Salesforce
, , , , ,
1

Overview

Salesforce has recently announced that they will retire the legacy SOAP-based login() authentication method starting Summer ’27. This mainly impacts integrations that still rely on username, password, and security token–based authentication.

To avoid any future authentication failures or unexpected production issues, Salesforce strongly recommends switching to OAuth 2.0 authentication.

In this article, we’ll explain:

  • What exactly is changing in Salesforce
  • Who is impacted
  • Why OAuth is now required
  • How to configure OAuth in ZappySys
  • How to migrate your existing packages safely

Applies To

What Is Changing in Salesforce?

Salesforce is retiring the SOAP API login() method for authentication in API versions 31.0 through 64.0, and this method will be fully disabled starting Summer ’27.

Official Salesforce announcement:

What does this mean?

If your integration is still using username + password + security token, Salesforce will block those login requests, which can cause:

  • Connection failures
  • Package execution errors
  • Broken production workflows

To prevent this, Salesforce recommends moving all integrations to OAuth-based authentication.

How Does This Affect ZappySys Users?

:white_check_mark: If You Are Already Using OAuth

No action is required. Your integrations will continue to work normally.

:warning: If You Are Using Username / Password Authentication

If your Salesforce connection in ZappySys is configured using legacy login, you will need to migrate to OAuth to avoid service disruption.

This applies to:

  • Existing SSIS packages
  • Scheduled SQL Agent jobs
  • Power BI refresh workflows using ODBC
  • API Connector jobs

:backhand_index_pointing_right: We strongly recommend migrating to OAuth as early as possible.

Why Switch to OAuth?

Besides being required by Salesforce, OAuth also provides:

  • Better security
  • Token-based authentication (no stored passwords)
  • Automatic token refresh
  • Long-term compatibility with Salesforce API changes

In short — OAuth is safer, more reliable, and future-proof.

How to Configure Salesforce OAuth in ZappySys

Below are the recommended steps to configure OAuth authentication for Salesforce connections in ZappySys.

Step 1 – Create a Connected App in Salesforce

  1. Log in to Salesforce
  2. Go to Setup → App Manager → New Connected App
  3. Enter:
  • Connected App Name
  • API Name
  • Contact Email

  1. Enable: Enable OAuth Settings

  2. Enter Callback URL:
    https://zappysys.com/oauth

  3. Select OAuth Scopes:

  • Full access (full)
  • Perform requests on your behalf (refresh_token, offline_access)
  • Access and manage your data (api)
  1. Click Save
  2. Copy the following values — you will need them in ZappySys:
  • Consumer Key (Client ID)
  • Consumer Secret (Client Secret)

Step 2 – Configure OAuth in ZappySys

  1. Open your SSIS Package
  2. Edit the Salesforce Connection Manager
  3. Set: Authentication Type = OAuth
  4. Enter:
  • Client ID
  • Client Secret
  1. Click Get New Token
  2. Log in to Salesforce and approve the access request
  3. Save the connection

Step 3 – Test Your Connection

Click Test Connection to confirm everything is working correctly.

How to Migrate Existing Packages Safely

If your current packages are using username/password authentication, follow these steps:

  1. Open Salesforce Connection Manager
  2. Change authentication to OAuth
  3. Complete OAuth setup
  4. Test the connection
  5. Redeploy your SSIS packages
  6. Run a test execution

This ensures your workflows continue running without interruption.

When Should You Migrate?

Salesforce will fully disable SOAP login in Summer ’27, but we recommend migrating well before that deadline to avoid last-minute issues.

Best practice: Plan and complete migration as early as possible.

Frequently Asked Questions

Will my existing integrations stop working?

Only if they are still using legacy username/password authentication. OAuth-based connections are not affected.

Does ZappySys fully support OAuth?

Yes. ZappySys provides native OAuth support with automatic token refresh, suitable for production and scheduled workloads.

Does this affect REST or Bulk APIs?

No. This change only impacts SOAP-based authentication. REST and Bulk APIs continue to work normally with OAuth.

Final Notes

Salesforce is making this change to improve security, compliance, and platform stability. Migrating to OAuth ensures your integrations remain reliable and future-proof.

If you need help configuring OAuth or migrating your existing packages, ZappySys Support Team is always happy to help.