Authorization for the Internet of Things using OAuth 2.0
draft-ietf-ace-oauth-authz-01

The information below is for an old version of the document
Document Type Active Internet-Draft (ace WG)
Last updated 2016-06-01 (latest revision 2016-02-25)
Replaces draft-tschofenig-ace-oauth-iot, draft-tschofenig-ace-oauth-bt, draft-seitz-ace-oauth-authz
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestones: Jul 2018 - WGLC for OAuth Authe..., Nov 2018 - Submit "Authenticati... )
Document shepherd Kepeng Li
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to "Kepeng Li" <kepeng.lkp@alibaba-inc.com>
ACE Working Group                                               L. Seitz
Internet-Draft                                                      SICS
Intended status: Standards Track                             G. Selander
Expires: August 28, 2016                                        Ericsson
                                                           E. Wahlstroem
                                                              S. Erdtman
                                                        Nexus Technology
                                                           H. Tschofenig
                                                                ARM Ltd.
                                                       February 25, 2016

        Authorization for the Internet of Things using OAuth 2.0
                     draft-ietf-ace-oauth-authz-01

Abstract

   This memo defines how to use OAuth 2.0 as an authorization framework
   with Internet of Things (IoT) deployments, thus bringing a well-known
   and widely used security solution to IoT devices.  Where possible
   vanilla OAuth 2.0 is used, but where the limitations of IoT devices
   require it, profiles and extensions are provided.

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 August 28, 2016.

Copyright Notice

   Copyright (c) 2016 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

Seitz, et al.            Expires August 28, 2016                [Page 1]
Internet-Draft         OAuth 2.0 IoT Authorization         February 2016

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  OAuth 2.0 . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  CoAP  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Object Security . . . . . . . . . . . . . . . . . . . . .   8
   4.  Protocol Interactions . . . . . . . . . . . . . . . . . . . .   9
   5.  OAuth 2.0 Profiling . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  Client Information  . . . . . . . . . . . . . . . . . . .  12
     5.2.  CoAP Access-Token Option  . . . . . . . . . . . . . . . .  15
     5.3.  Authorization Information Resource at the Resource Server  15
       5.3.1.  Authorization Information Request . . . . . . . . . .  16
       5.3.2.  Authorization Information Response  . . . . . . . . .  16
         5.3.2.1.  Success Response  . . . . . . . . . . . . . . . .  16
         5.3.2.2.  Error Response  . . . . . . . . . . . . . . . . .  16
     5.4.  Authorization Information Format  . . . . . . . . . . . .  17
     5.5.  CBOR Data Formats . . . . . . . . . . . . . . . . . . . .  17
     5.6.  Token Expiration  . . . . . . . . . . . . . . . . . . . .  17
   6.  Deployment Scenarios  . . . . . . . . . . . . . . . . . . . .  18
     6.1.  Client and Resource Server are Offline  . . . . . . . . .  19
     6.2.  Resource Server Offline . . . . . . . . . . . . . . . . .  22
     6.3.  Token Introspection with an Offline Client  . . . . . . .  26
     6.4.  Always-On Connectivity  . . . . . . . . . . . . . . . . .  30
     6.5.  Token-less Authorization  . . . . . . . . . . . . . . . .  31
     6.6.  Securing Group Communication  . . . . . . . . . . . . . .  34
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  35
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  35
     8.1.  CoAP Option Number Registration . . . . . . . . . . . . .  35
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  36
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  36
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  36
Show full document text