
Between now and Summer ’27, Salesforce changes how integrations sign in several times over, and one user setting changes with them. The integrations most likely to break are the quiet ones, like the quarterly sync or the year-end export nobody has opened since it was built.
Each change is a retirement or a tighter rule, and each has its own date. Here’s the order they land in, and how we’d find what’s at risk before each one.
The dates, in order:
Winter ’27 is generally available October 12, 2026, after the final upgrade weekend of October 9 and 10. The sign-in changes run well past that.
- With Winter ’27. Salesforce Ben lists a release update that rejects SOAP API login() for users without the Use Any API Auth permission. Sources disagree on the date, so check it under Release Updates in your own org’s Setup.
- November 4, 2026. In production, refresh tokens expire after 30 days of inactivity. Salesforce says this may break low-frequency integrations.
- November 30, 2026. The OAuth 2.0 device flow is restricted. The release update to look for is Restrict the OAuth 2.0 Device Flow to Local External Client Apps.
- December 1, 2026. This one affects users, not integrations. If Support once turned off email change verification for your org, that setting is removed. The replacement is a per-domain setting under Authorized Email Domains.
- February 20, 2027. The username-password, user-agent, and hybrid user-agent flows retire.
- Summer ’27. Salesforce retires SOAP login() in API versions 31.0 through 64.0. Its architect blog also says support for connected apps “ends by Summer ’27” and tells teams to start migrating to external client apps.
Why the quiet integrations break first
Of the dates still ahead, November 4 is the one we’d plan for first. From then on, a production refresh token that sits unused for 30 days expires.
An integration that runs every day never notices. One that runs once a quarter goes about three months between runs, well past 30 days, so its token can expire before the next run. Year-end jobs are in the same spot.
These are also the hardest integrations to find. If something hasn’t run lately, it won’t show up in recent login records, and the person who set it up may not remember it exists. So the inventory has to start with people as well as logs. Ask each team what runs monthly, quarterly, or once a year, and how it will get a new token after November 4.
February 20 retires three flows
The username-password flow is the one where an integration signs in with a username, a password, and a security token. The same date also retires the user-agent and hybrid user-agent flows. An inventory that only looks for password logins will miss any connected app using those two.
When the date hits, an affected integration’s token request fails. You’d look for it in that integration’s own logs and in Login History.
Salesforce names the replacements. For server-to-server integrations, it points to the client credentials flow. For integrations where a person signs in, it’s the web-server flow with PKCE.
You can rehearse the password-flow part of the cutoff now. Setup has a setting under OAuth and OpenID Connect Settings called Allow OAuth Username-Password Flows. We’d turn it off in a full or partial sandbox and see what breaks. Salesforce doesn’t describe this as a test. It’s just how we’d approach it. The setting is named for the username-password flow, so don’t read a clean test as covering the user-agent or hybrid user-agent flows. A sandbox also only tells you about the integrations pointed at it, so it doesn’t replace the inventory.
SOAP login() runs on its own clock
SOAP API login() also signs in with a username, a password, and a security token. It isn’t part of the February 20 retirement. It has its own deadlines.
Users without the Use Any API Auth permission get their login() requests rejected. Release Updates in your org shows when that starts. Then Summer ’27 retires login() in API versions 31.0 through 64.0. For the move, Salesforce lists the JWT bearer flow for server-to-server work and the client credentials flow for headless integrations. Browser-based apps move to the web server flow.
To find these logins, filter Login History for Login Type Other Apex API or Partner Product, with Login Subtype SOAP API. If you have Event Monitoring, review API Total Usage events where the connected app ID is empty.
That empty ID matters. A login that doesn’t come through a connected app won’t appear in a connected-app inventory, so SOAP logins need their own search.
How we’d build the inventory
We’d work through it like this.
- Open Release Updates in Setup and note the dates your org shows for the SOAP permission, the device flow, and the username-password retirement.
- Give integration users that still call SOAP login() the Use Any API Auth permission, and check Login History for failed API logins since your upgrade weekend.
- In Login History, filter by Login Type and Login Subtype, and list every app and user that shows up.
- Ask each team what runs monthly, quarterly, or once a year, and add anything Login History missed.
- For each integration, write down how it signs in (which OAuth flow, or SOAP login()), who owns it, and how often it runs.
- Flag anything that runs less than once a month for November 4, and ask its owner how it will reconnect.
- Match every username-password, user-agent, or hybrid user-agent flow to its replacement, with a date to switch well before February 20. Plan each SOAP login() move before Summer ’27.
What this means for your team
Every integration deadline here comes down to the same inventory. For each integration, it says how it signs in, who owns it, and how often it runs. If you don’t have one, build it now, while November 4 is still weeks away. With it, each date becomes a planned change with an owner.
If you’d like help building it, our team can walk through your Login History and integrations with you on a free call. Book a time with us.





