Additional OAuth Parameters for Authorization in Constrained Environments (ACE)
draft-ietf-ace-oauth-params-04

Document Type Active Internet-Draft (ace WG)
Last updated 2019-03-05 (latest revision 2019-02-11)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Jim Schaad
Shepherd write-up Show (last changed 2019-03-02)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Benjamin Kaduk
Send notices to Jim Schaad <ietf@augustcellars.com>
ACE Working Group                                               L. Seitz
Internet-Draft                                                      RISE
Intended status: Standards Track                       February 11, 2019
Expires: August 15, 2019

      Additional OAuth Parameters for Authorization in Constrained
                           Environments (ACE)
                     draft-ietf-ace-oauth-params-04

Abstract

   This specification defines new parameters for the OAuth 2.0 token and
   introspection endpoints when used with the framework for
   authentication and authorization for constrained environments (ACE).
   These are used to express the proof-of-possession key the client
   whishes to use, the proof-of-possession key that the AS has selected,
   and the key the RS should use to authenticate to the client.

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 https://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 15, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Seitz                    Expires August 15, 2019                [Page 1]
Internet-Draft              ACE-OAuth-Params               February 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Parameters for the Token Endpoint . . . . . . . . . . . . . .   3
     3.1.  Client-to-AS Request  . . . . . . . . . . . . . . . . . .   3
     3.2.  AS-to-Client Response . . . . . . . . . . . . . . . . . .   4
     3.3.  The Resource Server Confirmation Claim  . . . . . . . . .   6
   4.  Parameters for the Introspection Endpoint . . . . . . . . . .   6
     4.1.  AS-to-RS Response . . . . . . . . . . . . . . . . . . . .   6
   5.  Confirmation Method Parameters  . . . . . . . . . . . . . . .   7
   6.  CBOR Mappings . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  JSON Web Token Claims . . . . . . . . . . . . . . . . . .   9
     9.2.  CBOR Web Token Claims . . . . . . . . . . . . . . . . . .   9
     9.3.  OAuth Parameter Registration  . . . . . . . . . . . . . .   9
     9.4.  OAuth Introspection Response Parameter Registration . . .  10
     9.5.  Token Endpoint CBOR Mappings Registraton  . . . . . . . .  10
     9.6.  Introspection Endpoint CBOR Mappings Registraton  . . . .  10
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Appendix A.  Overlap with OAuth work  . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The Authentication and Authorization for Constrained Environments
   (ACE) specification [I-D.ietf-ace-oauth-authz] requires some new
   parameters for interactions with the OAuth 2.0 [RFC6749] token and
   introspection endpoints, as well as some new claims to be used in
   access tokens.  These parameters and claims can also be used in other
   contexts, and may need to be updated to align them with ongoing OAuth
   work.  Therefore they have been split out into this document, which
   can be used and updated independently of [I-D.ietf-ace-oauth-authz].

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
Show full document text