20 Feb 2027 · in 3 months
Salesforce is retiring the OAuth user-agent flow and the OAuth hybrid user-agent flow. For better security, update your integrations to use the OAuth web-server flow or hybrid web-server flow with the Proof Key for Code Exchange (PKCE) extension.
What to do Update integrations that use the OAuth user-agent or hybrid user-agent flows to use the web-server or hybrid web-server flow with PKCE before Spring '27.
20 Feb 2027 · in 3 months
When this release update is enforced, we'll stop supporting the OAuth 2.0 username-password flow for connected apps. This update will break all connected app integrations that use this flow.
What to do Move Connected App integrations off the OAuth 2.0 username-password flow before Spring '27, since those integrations will break when it is retired.
In the paper: Spring '27 release updates that need testing before enforcement, part one, Salesforce retires the OAuth username password flow and guides migration to client credentials
Set field visibility for guest users without affecting your settings for other external users. Turn on Independent Guest Field Masking to hide certain fields specifically from guest users.
What to do Turn on Independent Guest Field Masking and set field visibility so personal information is hidden from guest users without changing other external users' settings.
In the paper: Spring '27 release updates to Test before enforcement, part two
To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of To Do lists and Lightning dual listboxes when viewed at high magnification. This is part of our effort to comply with WCAG 2.2 Resize and Reflow guidelines.
What to do Test To Do lists and Lightning dual listboxes at zoom levels above 200% in Lightning Experience before Spring '27 enforcement.
In the paper: Spring '27 release updates that need testing before enforcement, part one
To improve security, Salesforce is removing non-public system fields from custom object data returned in Aura action responses. This update filters out internal system fields that aren’t part of the public Salesforce API.
What to do Check Aura components that rely on non-public system fields in Custom Object data, since those fields will be removed from action responses in Spring '27.
In the paper: Spring '27 release updates that need testing before enforcement, part one
With this update enabled, Visualforce pages rendered with renderAs="pdf" use the accessible PDF rendering engine, which produces tagged PDF/UA output. Tagged PDFs include the document structure and metadata that assistive technologies such as screen readers rely on.
What to do Evaluate Visualforce pages that use renderAs="pdf" in the beta accessible PDF rendering engine to produce tagged PDF/UA output before Spring '27.
This update rolls back the transaction of a platform event Apex trigger when it throws an unhandled exception, so that partially written records are no longer committed.
What to do Review Platform Event Apex triggers for unhandled exceptions, since their transactions will roll back instead of committing partial records in Spring '27.
In the paper: Spring '27 release updates to Test before enforcement, part two
The password and OAuth 2.0 authentication methods for the Salesforce Connect cross-org adapter are being retired. These authentication methods rely on the SOAP login() call, which is being retired.
What to do Plan to move Salesforce Connect cross-org adapter connections off password and OAuth 2.0 authentication before Spring '27.
Salesforce to Salesforce is being retired in Spring ’27. Salesforce has more powerful and integrated solutions that align with modern business needs.
What to do Plan a migration away from Salesforce to Salesforce before Spring '27, since the feature is being retired.
In the paper: Choosing replacements for Salesforce to Salesforce before its Spring '27 retirement, Spring '27 release updates that need testing before enforcement, part one, Winter ’27 release guides architects through security enforcement and agent scaling
In Summer ‘27, the SOAP API login() call in SOAP API versions 31.0 through 64.0 will no longer be supported and no longer be available.
What to do Replace SOAP API login() calls in API versions 31.0 through 64.0 with supported authentication before Summer '27, when the call is no longer available.
To optimize performance after large-scale updates to groups or roles, Salesforce now performs some sharing recalculations asynchronously. If Apex code and flows require that share records be updated immediately, the code and flows can break when this release update is enforced.
What to do Review Apex code and flows that need share records updated immediately after group or role changes, and make them handle asynchronous sharing recalculation.
To prevent disruption when Salesforce ends support for API traffic that uses an incorrect instanced URL, make sure that API traffic to your org uses the org’s My Domain login URL. First available in Summer ’25, this release update was scheduled to be enforced in Spring ’26, but we postponed enforcement to a phased schedule that starts in October 2026 in sandboxes and January 2027 in production.
What to do Update API traffic to use the org's My Domain login URL instead of incorrect instanced URLs, starting with sandboxes in October 2026 and production in January 2027.
Control access to Setup Audit Trail with the dedicated View Setup Audit Trail permission. Admins can provide access without granting the broader View Setup permission, supporting the principle of least privilege.
What to do Assign the View Setup Audit Trail permission to users who need Setup Audit Trail access, instead of granting the broader View Setup permission.
In the paper: Spring '27 release updates to Test before enforcement, part two