RFC 8628 - OAuth 2.0 Device Authorization Grant

Publication Date: August 2019
Status: Standards Track Document
Authors: W. Denniss (Google), J. Bradley (Ping Identity), M. Jones (Microsoft), H. Tschofenig (ARM Limited)

Abstract

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.

Table of Contents

• 1. Introduction
• 2. Terminology
• 3. Protocol
  • 3.1. Device Authorization Request
  • 3.2. Device Authorization Response
  • 3.3. User Interaction
    • 3.3.1. Non-Textual Verification URI Optimization
  • 3.4. Device Access Token Request
  • 3.5. Device Access Token Response
• 4. Discovery Metadata
• 5. Security Considerations
  • 5.1. User Code Brute Forcing
  • 5.2. Device Code Brute Forcing
  • 5.3. Device Trustworthiness
  • 5.4. Remote Phishing
  • 5.5. Session Spying
  • 5.6. Non-Confidential Clients
  • 5.7. Non-Visual Code Transmission
• 6. Usability Considerations
  • 6.1. User Code Recommendations
  • 6.2. Non-Browser User Interaction
• 7. IANA Considerations
  • 7.1. OAuth Parameter Registration
  • 7.2. OAuth URI Registration
  • 7.3. OAuth Extensions Error Registration
  • 7.4. OAuth Authorization Server Metadata
• 8. Normative References
• Acknowledgements
• Authors' Addresses

---

Copyright Notice: This document is subject to BCP 78 and the IETF Trust's Legal Provisions. For details, visit https://trustee.ietf.org/license-info.