RFC 8628: OAuth 2.0 Device Authorization Grant
In plain English — editorial summary, not part of the RFC
The OAuth 2.0 device authorization grant is designed for Internet- connected devices that either lack a browser to perform a user-agent- based authorization or are input constrained to the extent that requiring the user to input text in order to authenticate during the authorization flow is impractical. It enables OAuth clients on such devices (like smart TVs, media consoles, digital picture frames, and printers) to obtain user authorization to access protected resources by using a user agent on a separate device.
Document record
- Document ID
- RFC8628
- Published
- August 2019
- Authors
- W. Denniss; J. Bradley; M. Jones; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9202Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)Updated
August 2022
- RFC 9237An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)Current
August 2022
- RFC 9430Extension of the Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE) to Transport Layer Security (TLS)Current
July 2023
- RFC 7744Use Cases for Authentication and Authorization in Constrained EnvironmentsCurrent
January 2016
- RFC 7641Observing Resources in the Constrained Application Protocol (CoAP)Updated
September 2015
- RFC 8576Internet of Things (IoT) Security: State of the Art and ChallengesCurrent
April 2019
- RFC 9200Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)Current
August 2022
- RFC 9201Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)Current
August 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?