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.
Restricting how and when the device flow can be used increases security and helps protect your Salesforce data from illegitimate use of the flow.
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.
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:
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.
Starting in August 2026, a local external client app with the device flow enabled shows this informational banner, even when it's compliant:
A non-compliant app with the device flow enabled shows this warning:
You can also experience these behaviors:
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.
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.
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'
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.
For every app that must continue using the device flow, configure a local external client app that meets all of these conditions:
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.
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 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.
Note: Beginning November 30, 2026, there is no opt-out for non-compliant apps.
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.
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.
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.
Contact the app developer and ask for a compliant version before November 30, 2026. Test the updated version before deploying it to production.
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.
005461280

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.