Loading
Slack 관련 문의처가 Salesforce Help로 통합 및 변경됩니다.더 많이 읽기

Security Change: OAuth User-Agent Flow Retirement by February 20, 2027

게시 일자: Oct 19, 2026
상세 설명

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.

Why Salesforce Is Making This Change

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.

When the Change Takes Effect

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.

Who Is Affected

This change applies to Lightning Experience and Salesforce Classic in all editions. You are affected if an integration uses any of these login subtypes:

  • OAuth User-Agent
  • OAuth User-Agent for Hybrid Apps
  • OAuth User-Agent with ID Token

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.

What to Expect When the Flows Are Blocked or Retired

  • Integrations that use the user-agent or hybrid user-agent flow can't complete authorization and stop working.
  • For an authenticated user, Login History shows the status User-Agent Flow Disabled.
  • Attempts by unauthenticated users aren't recorded in Login History.
  • The redirect to /services/oauth2/authorize fails.

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.

Before Enforcement: How to Prepare

  1. Identify integrations that use the user-agent or hybrid user-agent flow.
  2. In a sandbox, migrate each affected integration to the appropriate secure OAuth flow.
  3. For a user-agent integration, migrate to the OAuth 2.0 web-server flow with PKCE.
  4. For a hybrid user-agent integration, migrate to the OAuth 2.0 hybrid web-server flow with PKCE.
  5. For an app that you didn't develop, contact the app developer and confirm that an updated version will be available before enforcement.
  6. In the sandbox, turn off Allow OAuth User-Agent Flows to test the effect of the retirement.
  7. Test every affected integration and review failed attempts until all integrations work while the insecure flows are blocked.
  8. Copy the tested changes to production.

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.

Identify Affected Apps


Option 1: Review Login History

  1. From Setup, in the Quick Find box, enter Login History, and then select Login History.
  2. Make sure the Login Subtype column appears. If it doesn't, edit the view or create a view that includes it.
  3. Find entries where Login Subtype is OAuth User-Agent, OAuth User-Agent for Hybrid Apps, or OAuth User-Agent with ID Token.


Option 2: Run a SOQL Query

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.

Test by Blocking the Retired Flows

Complete these steps in a sandbox first.

  1. From Setup, in the Quick Find box, enter OAuth, and then select OAuth and OpenID Connect Settings.
  2. Turn off Allow OAuth User-Agent Flows. This setting blocks both the user-agent flow and hybrid user-agent flow.
  3. Test integrations that could rely on either flow.
  4. For authenticated attempts, review Login History for User-Agent Flow Disabled.
  5. Check for failed redirects to /services/oauth2/authorize and the invalid_grant error.
  6. Update affected integrations or work with their developers.
  7. Continue testing until all integrations work while the setting is turned off.


After Enforcement: Resolve Authorization Failures

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.

  1. Identify the affected app from Login History, application logs, or the failed authorization request.
  2. Determine whether the app uses the user-agent flow or hybrid user-agent flow.
  3. Migrate a user-agent integration to the OAuth 2.0 web-server flow with PKCE.
  4. Migrate a hybrid user-agent integration to the OAuth 2.0 hybrid web-server flow with PKCE.
  5. If you don't own the app, obtain a compliant version from its developer.
  6. Test the updated authorization flow and the related business process in a sandbox.
  7. Deploy the tested update to production.


Impact on custom Mobile apps built using Salesforce Mobile SDK

Beginning in Mobile SDK 11.0,  OAuth 2.0 Web Server Flow is the default authentication flow.

  • If you’ve built a custom app that is using an older version of Salesforce Mobile SDK, you need to upgrade to the latest Mobile SDK version as soon as possible, so that you get enough time for all your users to install the updated app before the User-Agent flow retirement deadline.
  • If you are already on Mobile SDK 11.0+, but have explicitly opted out of Web Server flow, at the minimum, you need to revert to using Web Server flow as default. We strongly recommend upgrading to latest Mobile SDK version (14.0.0) to be prepared for this and other security mandates. The User-Agent Flow is deprecated in Mobile SDK 14.0.0 and will be removed in Mobile SDK 15.0.0


Impact on Salesforce Owned Mobile Apps

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.

Frequently Asked Questions


Which OAuth flow should replace the user-agent flow?

Use the OAuth 2.0 web-server flow with the PKCE extension.

Which OAuth flow should replace the hybrid user-agent flow?

Use the OAuth 2.0 hybrid web-server flow with the PKCE extension.

Does turning off Allow OAuth User-Agent Flows block both retired flows?

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.

Why doesn't a failed attempt appear in Login History?

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.

What should I do if I don't own the affected app?

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.

Why does the integration fail in a new org but still work in an older org?

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.

Knowledge 기사 번호

005461282

 
로드 중
Salesforce Help | Article