OAuth 2.0 Device Flow for Browserless and Input Constrained Devices
draft-ietf-oauth-device-flow-05

Document Type Active Internet-Draft (oauth WG)
Last updated 2017-04-10 (latest revision 2017-03-13)
Replaces draft-denniss-oauth-device-flow
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Apr 2017 - Submit 'OAuth 2.0 De... )
Document shepherd Rifaat Shekh-Yusef
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
OAuth                                                         W. Denniss
Internet-Draft                                                    Google
Intended status: Standards Track                              J. Bradley
Expires: September 14, 2017                                Ping Identity
                                                                M. Jones
                                                               Microsoft
                                                           H. Tschofenig
                                                             ARM Limited
                                                          March 13, 2017

  OAuth 2.0 Device Flow for Browserless and Input Constrained Devices
                    draft-ietf-oauth-device-flow-05

Abstract

   This OAuth 2.0 authorization flow for browserless and input
   constrained devices, often referred to as the device flow, enables
   OAuth clients to request user authorization from devices that have an
   Internet connection, but don't have an easy input method (such as a
   smart TV, media console, picture frame, or printer), or lack a
   suitable browser for a more traditional OAuth flow.  This
   authorization flow instructs the user to perform the authorization
   request on a secondary device, such as a smartphone.  There is no
   requirement for communication between the constrained device and the
   user's secondary device.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 14, 2017.

Denniss, et al.        Expires September 14, 2017               [Page 1]
Internet-Draft            OAuth 2.0 Device Flow               March 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Device Authorization Request  . . . . . . . . . . . . . .   5
     3.2.  Device Authorization Response . . . . . . . . . . . . . .   6
     3.3.  User Instruction  . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Device Access Token Request . . . . . . . . . . . . . . .   8
     3.5.  Device Access Token Response  . . . . . . . . . . . . . .   9
   4.  Discovery Metadata  . . . . . . . . . . . . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
     5.1.  User Code Brute Forcing . . . . . . . . . . . . . . . . .  10
     5.2.  Device Trustworthiness  . . . . . . . . . . . . . . . . .  10
     5.3.  Remote Phishing . . . . . . . . . . . . . . . . . . . . .  10
     5.4.  Non-confidential Clients  . . . . . . . . . . . . . . . .  11
     5.5.  Non-Visual Code Transmission  . . . . . . . . . . . . . .  11
   6.  Usability Considerations  . . . . . . . . . . . . . . . . . .  11
     6.1.  User Code Recommendations . . . . . . . . . . . . . . . .  11
     6.2.  Non-Browser User Interaction  . . . . . . . . . . . . . .  12
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  OAuth URI Registration  . . . . . . . . . . . . . . . . .  12
       7.1.1.  Registry Contents . . . . . . . . . . . . . . . . . .  12
     7.2.  OAuth Extensions Error Registration . . . . . . . . . . .  12
       7.2.1.  Registry Contents . . . . . . . . . . . . . . . . . .  12
     7.3.  OAuth 2.0 Authorization Server Metadata . . . . . . . . .  13
       7.3.1.  Registry Contents . . . . . . . . . . . . . . . . . .  13
Show full document text