Salesforce is retiring the OAuth 2.0 username-password flow for connected apps. After enforcement, connected app integrations that use this flow can no longer obtain access tokens. This update was first announced in Spring '26. See also the latest Summer '26 Release Note.
This article answers the question: what is changing with the OAuth 2.0 username-password flow for Salesforce connected apps on February 20, 2027, and how do you prepare your integrations? It explains the change, who is affected, what to expect, and the steps to take before and after enforcement.
On February 20, 2027, Salesforce stops supporting the OAuth 2.0 username-password flow for connected apps. After enforcement, connected app integrations that use this flow can no longer obtain access tokens.
The username-password flow sends a user's credentials directly in an HTTP request. Retiring this flow increases security and better protects your Salesforce data.
Salesforce enforces this update on February 20, 2027.
This change applies to Lightning Experience and Salesforce Classic in all editions.
You're affected if a connected app integration uses the OAuth 2.0 username-password flow. This includes custom integrations and apps installed from managed packages.
If the Retirement of OAuth 2.0 Username-Password Flow for Connected Apps release update doesn't appear in your org, the flow is already blocked in your OAuth and OpenID Connect settings, and this change doesn't affect you.
After Salesforce blocks or retires the flow, the following behavior occurs:
{
"error": "invalid_grant",
"error_description": "authentication failure"
}
In plain text, the failed token request returns the error invalid_grant with the description "authentication failure". The message shown to end users depends on how the app handles the failed token request.
For detailed testing and activation instructions, log in to your org. From Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. Open Retirement of OAuth 2.0 Username-Password Flow for Connected Apps and follow the testing and activation steps.
Use the English LoginSubType value exactly as shown.
SELECT Application FROM LoginHistory WHERE LoginSubType = 'OAuth Username-Password'
In plain text, this query returns the Application value from each LoginHistory record where the LoginSubType is OAuth Username-Password, which lists the apps that still use the username-password flow.
Note: After Salesforce enforces this change on February 20, 2027, there is no opt-out. Re-enabling the username-password flow isn't a supported resolution.
For end-user login and authorization, use the OAuth 2.0 web-server flow with the Proof Key for Code Exchange (PKCE) extension. For server-to-server integrations, use the OAuth 2.0 client credentials flow.
Contact the app developer and confirm that they will provide an updated version before February 20, 2027. Test the updated version before deploying it to production.
If the release update isn't listed, the username-password flow is already blocked in your OAuth and OpenID Connect settings. The retirement doesn't require further action for that org, but you should verify that your integrations are working as expected.
005461279

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.