Group OSCORE Profile of the Authentication and Authorization for Constrained Environments Framework
draft-tiloca-ace-group-oscore-profile-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01

ACE Working Group                                              M. Tiloca
Internet-Draft                                               R. Hoeglund
Intended status: Standards Track                                L. Seitz
Expires: May 7, 2020                                             RISE AB
                                                            F. Palombini
                                                             Ericsson AB
                                                       November 04, 2019

    Group OSCORE Profile of the Authentication and Authorization for
                   Constrained Environments Framework
                draft-tiloca-ace-group-oscore-profile-01

Abstract

   This document specifies a profile for the Authentication and
   Authorization for Constrained Environments (ACE) framework.  The
   profile uses Object Security for Constrained RESTful Environments
   (OSCORE) and/or Group OSCORE to provide communication security
   between a Client and (a group of) Resource Server(s).  Furthermore,
   the profile uses (Group) OSCORE to provide server authentication, and
   OSCORE to achieve proof-of-possession for a key owned by the Client
   and bound to an OAuth 2.0 Access Token.  Also, the profile provides
   proof-of-group-membership for the Client, by securely binding the
   pre-established Group OSCORE Security Context to the pairwise OSCORE
   Security Context newly established with the Resource Server.

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 May 7, 2020.

Tiloca, et al.             Expires May 7, 2020                  [Page 1]
Internet-Draft         Group OSCORE Profile of ACE         November 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Pre-Conditions  . . . . . . . . . . . . . . . . . . . . .   8
     2.2.  Access Token Retrieval  . . . . . . . . . . . . . . . . .   8
     2.3.  Access Token Posting  . . . . . . . . . . . . . . . . . .   9
     2.4.  Secure Communication  . . . . . . . . . . . . . . . . . .  10
   3.  Client-AS Communication . . . . . . . . . . . . . . . . . . .  10
     3.1.  C-to-AS: POST to Token Endpoint . . . . . . . . . . . . .  11
       3.1.1.  'context_id' Parameter  . . . . . . . . . . . . . . .  13
       3.1.2.  'salt' Parameter  . . . . . . . . . . . . . . . . . .  14
       3.1.3.  'client_cred' Parameter . . . . . . . . . . . . . . .  14
       3.1.4.  'client_cred_verify' Parameter  . . . . . . . . . . .  14
     3.2.  AS-to-C: Access Token . . . . . . . . . . . . . . . . . .  14
       3.2.1.  Client Credential Claim . . . . . . . . . . . . . . .  19
   4.  Client-RS Communication . . . . . . . . . . . . . . . . . . .  20
     4.1.  C-to-RS POST to authz-info Endpoint . . . . . . . . . . .  21
     4.2.  RS-to-C: 2.01 (Created) . . . . . . . . . . . . . . . . .  21
     4.3.  OSCORE Setup - Client Side  . . . . . . . . . . . . . . .  22
     4.4.  OSCORE Setup - Resource Server Side . . . . . . . . . . .  23
     4.5.  Access Rights Verification  . . . . . . . . . . . . . . .  25
   5.  Secure Communication with the AS  . . . . . . . . . . . . . .  26
   6.  Discarding the Security Context . . . . . . . . . . . . . . .  26
   7.  CBOR Mappings . . . . . . . . . . . . . . . . . . . . . . . .  27
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  27
   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  27
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  28