Edit Content

Welcome to Simploud Academy

Your one-stop hub for learning, troubleshooting, training, and staying updated with the latest features, resources, and news from Simploud.

Product Updates

Discover what’s new in Simploud. The Product Updates section provides details on new releases, feature enhancements, new processes, and performance improvements. Stay ahead with the latest tools designed to simplify compliance, strengthen quality processes, and give your team the flexibility to meet evolving regulatory and business needs.

SOAP Login API Retirement

Salesforce is implementing mandatory security changes to protect your data. Please review the two primary updates below and their respective deadlines.

What it is?

The SOAP API login() Operation is a legacy authentication method that has been used for over two decades to connect external applications to the Salesforce Platform. It allows a system to authenticate by passing a plain-text Username, Password, and Security Token. While straightforward, this “basic” authentication lacks the granular security controls and multi-factor authentication (MFA) compatibility of modern standards.

What is the change?

The Deadline: June 2027 (with the Summer ’27 release).

This retirement means that Salesforce will permanently disable the ability to log in using simple credentials; any integration still relying on the legacy login() call will fail to authenticate, resulting in immediate service disruption.

Impact on Simploud

  1. The Simploud product itself is built to modern standards and is not impacted by this retirement. The only exception within our ecosystem is the “Document Rendition for Large Documents” feature, which currently utilizes this legacy path. We have already scheduled the transition for this specific component, and it is planned to be resolved by Winter ’27, well ahead of the final retirement date.

Actions Required

While Simploud is handling the heavy lifting for our platform, you must audit any secondary, non-Simploud integrations that connect to your Salesforce instance. These often include:

  • Legacy Middleware: Older versions of ETL tools (like Informatica, Boomi, or Jitterbit) that haven’t been updated in several years.

     
  • Third-Party Tools: Any “set it and forget it” applications that were configured using a dedicated integration user and a security token.

If you have any integration that uses that username and password flow, reach out to the external service provider or the IT Team to migrate the authentication flow to OAuth 2.0 flows (such as the JWT Bearer Flow or Client Credentials Flow).