Salesforce is retiring the OAuth 2.0 user-agent flow and the OAuth 2.0 hybrid user-agent flow. After enforcement, apps can't use these flows to authorize users or obtain access tokens. Salesforce also begins blocking these flows in newly created orgs starting in the Winter '27 release. Existing integrations in older orgs can continue to work only until the final retirement date of February 20, 2027.
The user-agent and hybrid user-agent flows expose access tokens directly to the browser, so retiring them increases security and better protects your Salesforce data. For more information, see the latest Summer '26 Release Note.
This article explains the Salesforce OAuth user-agent and hybrid user-agent flow retirement, who is affected, how to prepare before February 20, 2027, and how to resolve authorization failures after enforcement.
The user-agent and hybrid user-agent flows expose access tokens directly to the browser. Retiring these flows increases security, helps keep access tokens safe, and better protects your Salesforce data.
The user-agent and hybrid user-agent flows are blocked in newly created orgs starting in the Winter '27 release. Existing integrations in older orgs continue to function until the final retirement date of February 20, 2027.
This change applies to Lightning Experience and Salesforce Classic in all editions. You are affected if an integration uses any of these login subtypes:
This includes custom integrations and apps installed from managed packages. If you don't own an affected app, contact the app developer for an updated version.
Before Salesforce enforces the retirement, a Salesforce Admin who blocks these flows causes the following invalid_grant response, which says an admin disabled the flow.
{
"error": "invalid_grant",
"error_description": "user-agent flow has been disabled by your Salesforce admin"
}
After Salesforce enforces the retirement, the response changes to the following invalid_grant response, which says Salesforce disabled the flow.
{
"error": "invalid_grant",
"error_description": "user-agent flow has been disabled by Salesforce"
}
The message shown to an end user depends on how the app handles this authorization error.
For Salesforce's guided testing and activation steps, log in to your org. From Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. Open OAuth User-Agent and Hybrid User-Agent Flows Retirement.
Use the English LoginSubType values exactly as shown. The following query returns the application name for every login that used one of the three retired login subtypes.
SELECT Application FROM LoginHistory WHERE LoginSubType IN ( 'OAuth User-Agent', 'OAuth User-Agent for Hybrid Apps', 'OAuth User-Agent with ID Token' )
Login History identifies recent usage. Also review app configurations and deployment documentation so that you don't overlook an integration that hasn't been used recently.
Complete these steps in a sandbox first.
Note: Beginning February 20, 2027, there is no opt-out. Re-enabling Allow OAuth User-Agent Flows isn't a supported resolution after Salesforce enforces the retirement.
Beginning in Mobile SDK 11.0, OAuth 2.0 Web Server Flow is the default authentication flow.
Salesforce owned mobile apps like Salesforce app, Mobile Publisher, Field Service, etc., have already migrated to Web Server Flow. End users should update their apps to the latest versions before February 20, 2027.
Use the OAuth 2.0 web-server flow with the PKCE extension.
Use the OAuth 2.0 hybrid web-server flow with the PKCE extension.
Yes. Turning off this setting blocks the user-agent flow and hybrid user-agent flow, which lets you test the effect of the retirement before enforcement.
The User-Agent Flow Disabled status is recorded only for authenticated users. An attempt by an unauthenticated user isn't recorded, so also review application logs and failed requests to /services/oauth2/authorize.
Contact the app developer and request a version that uses the appropriate web-server flow with PKCE. Test the updated app before February 20, 2027.
Salesforce blocks the retired flows in newly created orgs before the final enforcement date. Older orgs can continue using them temporarily, but all orgs must migrate before February 20, 2027.
005461282

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.