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

Security Change: OAuth 2.0 Device Flow Restrictions by November 30, 2026

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

Salesforce is restricting the OAuth 2.0 device flow to local external client apps with a localhost callback URL. Connected apps, packaged external client apps, and other non-compliant apps can no longer use the device flow after enforcement on November 30, 2026.

The device flow is intended only for apps that run on devices with limited input or display capabilities, such as smart TVs, appliances, and other Internet of Things (IoT) devices. See the latest Summer '26 Release Note.

솔루션

This article explains how Salesforce restricts the OAuth 2.0 device flow starting November 30, 2026, which apps are affected, and how to prepare your apps or fix authentication failures after enforcement.

Why Salesforce Is Making This Change

Restricting how and when the device flow can be used increases security and helps protect your Salesforce data from illegitimate use of the flow.

When the Change Takes Effect

Starting in August 2026, Salesforce displays new informational and warning banners in Setup and restricts some configuration changes for apps that use the device flow.

On November 30, 2026, Salesforce blocks the device flow for non-compliant apps.

Which Apps Are Affected

This change applies to connected apps and external client apps in all editions. An app is compliant only when it meets all of these requirements:

  • It's an external client app.
  • Its distribution state is set to Local.
  • Its callback URL is https://localhost.
  • No other OAuth flows are enabled in the app settings.

All connected apps with the device flow enabled are non-compliant. Packaged external client apps and local external client apps that don't meet every requirement are also non-compliant.

For apps that you didn't develop, including apps installed from managed packages, contact the app developer. The developer is responsible for providing an updated app before enforcement.

What to Expect in Setup

Starting in August 2026, a local external client app with the device flow enabled shows this informational banner, even when it's compliant:

  • "The OAuth device flow is enabled. Only use this flow with devices that run on limited input or display capabilities, such as Smart TVs, appliances, and other Internet of Things (IoT) devices."

A non-compliant app with the device flow enabled shows this warning:

  • "This app has the OAuth device flow enabled, but doesn't meet new security requirements. To continue using the device flow, switch to a local external client app with a localhost callback URL and don't use the app with any other OAuth flows."

You can also experience these behaviors:

  • You can't save changes to a non-compliant app while the device flow is enabled. Salesforce displays: "The OAuth device flow is supported only for local external client apps with a localhost callback URL. Disable the device flow or switch to a local external client app that you don't use with any other OAuth flows."
  • If you disable the device flow on a connected app or packaged external client app, you can't re-enable it unless you use a compliant local external client app.
  • For a connected app with the device flow disabled, the option to enable the flow is locked and hidden.
  • For a packaged external client app with the device flow disabled, the option to enable it is unavailable until the distribution state is changed to Local.
  • Enabling the device flow on a local external client app automatically changes the callback URL to https://localhost, removes other callback URL values, and disables other OAuth flows.
  • Beginning November 30, 2026, device-flow authentication fails for every non-compliant app.

How to Prepare Before Enforcement

  1. Identify apps that have used the device flow.
  2. Review connected apps and external client apps in Setup for the non-compliance warning banner.
  3. Migrate affected connected apps to local external client apps.
  4. Update or replace affected external client apps so that they meet every requirement.
  5. Update client-side code with new app credentials if you create a new app.
  6. Test every updated app that uses the device flow.
  7. After testing succeeds, copy the changes to production.

To review Salesforce's guided steps, from Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. Open Restrict the OAuth 2.0 Device Flow to Local External Client Apps and follow the testing and activation steps.

How to Identify Apps That Use the Device Flow

Login History contains up to six months of device-flow usage. It's a useful starting point, but it doesn't identify older apps that haven't been used recently.

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 Device.

Option 2: Run a SOQL Query

The following SOQL query returns the application name for every login history record where the login subtype is OAuth Device. Use the English LoginSubType value exactly as shown.

SELECT Application
FROM LoginHistory
WHERE LoginSubType = 'OAuth Device'

How to Review Apps for the Warning Banner

The warning banner appears only when the device flow is enabled and the app is non-compliant. If an app doesn't display the warning, it isn't affected by this release update in its current configuration.

Review Connected Apps

  1. From Setup, in the Quick Find box, enter App Manager, and then select App Manager.
  2. For each app with an app type of Connected, open the row-level action menu and select View.
  3. Look for the device-flow warning at the top of the page and record whether the app is affected.

Review External Client Apps

  1. From Setup, in the Quick Find box, enter External Client App Manager, and then select External Client App Manager.
  2. Select each external client app.
  3. Look for the device-flow warning at the top of the page and record whether the app is affected.

How to Update Affected Apps

For every app that must continue using the device flow, configure a local external client app that meets all of these conditions:

  • Distribution State is set to Local.
  • Enable Device Flow is turned on.
  • The callback URL is https://localhost.
  • No other OAuth flow is enabled.

The device flow doesn't use the callback URL directly. Salesforce uses its value to verify that the app meets the security requirements, so changing it to https://localhost doesn't alter the device flow itself.

Migrate a Connected App

Use the automated migration process for an eligible connected app. If the app isn't eligible, manually create a local external client app that mirrors it. In either case, set the distribution state to Local and turn on Enable Device Flow. Enabling the setting automatically configures https://localhost and disables other OAuth flows.

Update or Replace an External Client App

Update the existing app or create a new local external client app. Creating a new app is generally simpler when the existing app is packaged or uses multiple OAuth flows. If you create an app, update the client-side code with its new credentials, including the client ID and client secret.

How to Resolve Authentication Failures After Enforcement

Note: Beginning November 30, 2026, there is no opt-out for non-compliant apps.

  1. Review Login History for entries with the OAuth Device login subtype to identify the affected app.
  2. Confirm whether the app meets all four compliance requirements.
  3. If it's a connected app, migrate it to a local external client app.
  4. If it's an external client app, update it or replace it with a compliant local external client app.
  5. Update client-side code with new credentials when applicable.
  6. Test device-flow authentication and the related business process before deploying the update to production.
  7. If you don't own the app, contact its developer for a compliant version.

Frequently Asked Questions


Can a connected app continue using the OAuth 2.0 device flow?

No. All connected apps that have the device flow enabled are non-compliant. Migrate the app to a local external client app before November 30, 2026.

Can an app use the device flow and another OAuth flow?

No. A compliant device-flow app can't have other OAuth flows enabled. If the existing app requires multiple flows, create a separate local external client app for the device flow.

Why does enabling the device flow change my callback URL?

Salesforce uses https://localhost to confirm that the device flow is used only by a local external client app. The device flow doesn't directly use the callback URL. Enabling the flow automatically removes other callback URLs and disables other OAuth flows.

What if I don't own the affected app?

Contact the app developer and ask for a compliant version before November 30, 2026. Test the updated version before deploying it to production.

Why doesn't an app display the device flow warning banner?

The warning appears only when the device flow is enabled and the app is non-compliant. If the warning isn't present, the app isn't affected in its current configuration. You can still use Login History to confirm whether the app has recently used the device flow.

Knowledge 기사 번호

005461280

 
로드 중
Salesforce Help | Article