Salesforce will tighten where the OAuth 2.0 device flow can be used on 30 November 2026. From that date, authentication through the flow will fail unless the app is a local external client app with a localhost callback URL and no other OAuth flows enabled.

This is a focused change, not a retirement of OAuth generally. The device flow exists for applications on devices with limited input or display capabilities, such as appliances and other connected devices. Salesforce also notes that command-line applications can use it. A user completes approval in a browser while the originating device polls for authorisation.

Many organisations will have no affected app. Those that do have just over a month to confirm usage, choose whether the flow is still appropriate and test a compliant configuration. The deadline and platform behaviour below are confirmed by Salesforce. The inventory, governance and cutover recommendations are the Ostrelis view.

What Salesforce is changing

An app will be compliant only if it meets all four conditions:

  • it is an external client app;
  • its distribution state is Local;
  • its callback URL is https://localhost; and
  • no other OAuth flow is enabled in that app’s settings.

Every connected app with the device flow enabled is therefore non-compliant. Packaged external client apps are also non-compliant, as are local external client apps that do not meet every condition. Salesforce says there is no opt-out after enforcement.

The localhost value can look odd because the device flow does not use the callback URL directly. Salesforce uses it to verify the permitted configuration. Enabling device flow on a local external client app automatically sets the callback URL to https://localhost, removes other callback URLs and disables other OAuth flows.

An app currently used for several authentication patterns therefore cannot remain a shared container for device flow. The device-flow use case needs a dedicated compliant app, while the other flows must be provided separately.

Who should investigate

Salesforce administrators should coordinate the review, but they may not own the affected software. Integration teams, developers, security teams, release managers and suppliers may each hold part of the evidence.

Do not search only for televisions or industrial devices. Command-line tools, internally built utilities, field hardware and supplier products can use the flow. Conversely, an app being labelled “device”, “desktop” or “CLI” does not prove it uses OAuth device flow. Confirm the authentication behaviour and Salesforce configuration.

An installed package also deserves attention. Salesforce instructs customers who do not own an affected app to contact the developer for a compliant version. Establish the replacement version, new app type, expected credentials, test route and supported cutover plan—not simply whether the supplier is “aware”.

Find recent device-flow activity

Salesforce introduced an OAuth Device login subtype on a rolling basis from 17 August 2026. In Setup, review Login History with the Login Subtype column visible. Salesforce also documents this SOQL starting point:

SELECT Application
FROM LoginHistory
WHERE LoginSubType = 'OAuth Device'

Login History contains up to six months of usage, so it is useful evidence but not a complete inventory. An infrequently used disaster-recovery tool, seasonal device or dormant integration may not appear. Record the application, user, last activity, business process and owner for each match, then reconcile that list with App Manager, External Client App Manager, integration registers, source repositories and supplier records.

Salesforce says a warning banner appears when device flow is enabled on a non-compliant app. Review connected apps in App Manager and external client apps in External Client App Manager. The absence of a warning means the app is not affected in its current configuration, but it does not replace the usage review or prove that an older dependency can be discarded safely.

Choose the right response for each app

There are three sensible outcomes.

  1. Retire the use case. If the app is obsolete, remove it through the normal change and access-revocation process. Confirm that tokens, credentials and permissions are withdrawn rather than merely leaving the flow unused.
  2. Keep device flow in a dedicated local external client app. Migrate an eligible connected app using Salesforce’s process or create a new compliant app. A new app means new credentials and client-side configuration.
  3. Move to a different OAuth flow. If the software is not genuinely constrained by limited input, review supported alternatives with its developer and security owner. The replacement must fit whether a user is present, where secrets can be protected and how access should be governed.

Salesforce recommends creating a new local external client app when an existing external client app is packaged or uses multiple OAuth flows. That separation reduces the chance that enabling device flow unexpectedly breaks another authentication route.

Test more than the login screen

A successful token response is necessary, but it is not enough. Test the business action that follows authentication, including the permissions and scopes actually needed. Confirm token renewal, logout or revocation behaviour, error handling, retry limits and monitoring. Where the app is installed on physical or remote equipment, prove how configuration and new credentials will reach every active instance.

Use a representative non-production path. Salesforce’s Release Updates page provides guided testing and activation steps, but an organisation still needs its own evidence for connected systems and operational processes. Record who approved the result and how support will distinguish an old client ID from a service outage after enforcement.

Take care when changing an existing app. Since August 2026, Salesforce has restricted some edits to non-compliant apps. Disabling device flow on a connected app or packaged external client app cannot simply be undone in the old configuration. Make a rollback plan before altering a live authentication route.

A practical plan before 30 November

  1. Assign an owner. Give one person responsibility for the cross-org inventory and deadline, with named technical and business owners for each app.
  2. Use both evidence routes. Review OAuth Device login history and warning banners in App Manager and External Client App Manager.
  3. Check beyond recent logins. Reconcile dormant tools, command-line utilities, packages, connected equipment and supplier integrations.
  4. Decide deliberately. Retire the use case, create a dedicated compliant app or move to an appropriate supported flow.
  5. Obtain supplier commitments. Get version, configuration and testing details for products your organisation does not control.
  6. Prepare credential changes. Identify where client IDs and secrets are stored and how they are distributed without exposing them.
  7. Test the whole process. Cover authorisation, permissions, token handling, the business transaction, failure alerts and recovery.
  8. Monitor enforcement. On and after 30 November, watch authentication failures and Login History for clients still presenting the old app configuration.

The Ostrelis view

This deadline is narrower than other connected-app changes on the Salesforce roadmap, but it rewards the same discipline: know which application is authenticating, who owns it and why its selected flow is appropriate.

Avoid turning this into a blanket migration of every connected app. Start with evidence of device-flow configuration and usage. For affected apps, separation matters: the compliant destination is local, has a localhost callback and does not share other OAuth flows. That is an architectural boundary, not just a checkbox exercise.

Ostrelis can help organisations inventory Salesforce integrations, assess authentication dependencies, coordinate suppliers and plan controlled testing. See our Salesforce managed services, data and integration support and approach and experience. Need help getting prepared? Talk to a Salesforce expert.

Need help getting prepared?

Ostrelis can help assess whether this change affects your Salesforce environment, identify dependencies and plan the work needed to prepare safely.

Talk to a Salesforce expert

Sources

  1. Security Change: OAuth 2.0 Device Flow Restrictions by November 30, 2026 — Salesforce Help (7 October 2026, accessed 26 October 2026)
  2. Restrict the OAuth 2.0 Device Flow to Local External Client Apps — Salesforce Help — Release Notes (Winter ’27 release notes, accessed 26 October 2026)
  3. Monitor Usage of the OAuth 2.0 Device Flow — Salesforce Help — Release Notes (Winter ’27 release notes; available from 17 August 2026, accessed 26 October 2026)
  4. Connected App & External Client App Security Requirement Updates — Salesforce Help (7 October 2026, accessed 26 October 2026)
  5. OAuth 2.0 Device Flow for IoT Integration — Salesforce Help (Current Salesforce Help guidance, accessed 26 October 2026)