Overview
Salesforce Summer ’26 includes updates across the Salesforce platform, including Salesforce Core, APIs, authentication services, sandbox infrastructure, and packaging and deployment processes.
Riva has reviewed the Salesforce Summer ’26 release and confirmed that Riva supports this Salesforce release.
What This Means for Riva Customers
Riva supports Salesforce Summer ’26, and no Riva-specific action is required.
Customers can continue using Riva as usual before and after their Salesforce Summer ’26 upgrade. Standard Salesforce upgrade processes can be followed.
For this release:
- No Riva-specific configuration changes are required.
- No Riva package upgrade sequencing changes are required.
- No Riva migration activities are required.
- Standard Salesforce upgrade processes can be followed.
Items Riva Is Monitoring
Riva is aware of several Salesforce platform changes introduced or announced around the Summer ’26 release. These items are not expected to require customer action for Summer ’26, but Riva will continue to monitor them as part of ongoing compatibility planning.
SOAP API Login Changes
Salesforce has announced changes to SOAP API login behavior. Riva is aware of these changes and expects to make updated support available in upcoming Riva releases.
No customer action is required for Salesforce Summer ’26.
OAuth Username-Password Flow Retirement
Salesforce has announced a future retirement of the OAuth 2.0 username-password flow for connected apps. This change affects integrations that authenticate to Salesforce by directly using a Salesforce username and password.
For Riva On-Premise customers using Salesforce username/password authentication, updated support is expected to be available in the Riva 2026.3 release, planned for August 2026. For more information, see: Salesforce Username/Password Authentication Deprecation for Riva On-Premise.
If You Experience an Issue
If you experience an issue after your Salesforce Summer ’26 upgrade, contact Riva Support Team and include the Salesforce org version, a description of the issue, affected users or mailboxes, and any relevant sync logs or error messages.