# Opt in needed to keep OAuth Device Authorization Flow working

DevFeed: [Opt in needed to keep OAuth Device Authorization Flow working](<https://devfeed.tech/articles/opt-in-needed-to-keep-oauth-device-authorization-flow-working-74144.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2022-03-02-opt-in-needed-to-keep-oauth-device-authorization-flow-working>)

Author: Sidi Merzouk

Published: 2022-03-02T22:56:09Z

Content type: news

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [github](<https://devfeed.tech/tags/github.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [phishing](<https://devfeed.tech/tags/phishing.md>)

## AI overview

GitHub will require OAuth and GitHub Apps using the OAuth Device Authorization flow to opt in starting March 16, 2022. Apps that have not opted in will receive HTTP 400 responses from the flow's API endpoints. The change is intended to reduce phishing attacks against GitHub users.

## Source excerpt

On March 16 2022 the OAuth Device Authorization flow will become an "opt in" feature for all OAuth and GitHub Apps. This change reduces the likelihood of Apps being used...