JOSE Authentication
draft-hardt-gnap-jose-01

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

• Versions
• 00
• 01

Network Working Group                                      D. Hardt, Ed.
Internet-Draft                                                SignIn.Org
Intended status: Standards Track                             4 July 2020
Expires: 5 January 2021

                          JOSE Authentication
                        draft-hardt-gnap-jose-01

Abstract

   TBD

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 5 January 2021.

Copyright Notice

   Copyright (c) 2020 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  JOSE Authentication . . . . . . . . . . . . . . . . . . . . .   3

Hardt                    Expires 5 January 2021                 [Page 1]
Internet-Draft             JOSE Authentication                 July 2020

     2.1.  Grant Server Access . . . . . . . . . . . . . . . . . . .   4
       2.1.1.  Authorization Header  . . . . . . . . . . . . . . . .   4
       2.1.2.  Signed Body . . . . . . . . . . . . . . . . . . . . .   5
       2.1.3.  Public Key Resolution . . . . . . . . . . . . . . . .   6
     2.2.  Resource Server Access  . . . . . . . . . . . . . . . . .   7
       2.2.1.  JOSE header . . . . . . . . . . . . . . . . . . . . .   7
       2.2.2.  "jose" Mechanism  . . . . . . . . . . . . . . . . . .   7
       2.2.3.  "jose+body" Mechanism . . . . . . . . . . . . . . . .   8
       2.2.4.  Public Key Resolution . . . . . . . . . . . . . . . .   9
     2.3.  Request Encryption  . . . . . . . . . . . . . . . . . . .   9
     2.4.  Response Signing  . . . . . . . . . . . . . . . . . . . .   9
     2.5.  Response Encryption . . . . . . . . . . . . . . . . . . .  10
   3.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Appendix A.  Document History . . . . . . . . . . . . . . . . . .  11
     A.1.  draft-hardt-gnap-jose-00  . . . . . . . . . . . . . . . .  11
     A.2.  draft-hardt-gnap-jose-01  . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   TBD

   *Terminology*

   This document uses the following terms defined in [GNAP]:

   *  Authorization URI (AZ URI)

   *  Client

   *  Client Handle

   *  Registered Client

   *  Dynamic Client

   *  Grant

   *  Grant Server (GS)

   *  GS URI

   *  NumericDate

   *  Resource Server (RS)

Hardt                    Expires 5 January 2021                 [Page 2]
Internet-Draft             JOSE Authentication                 July 2020

   *Notational Conventions*

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   specification are to be interpreted as described in [RFC2119].

   Certain security-related terms are to be understood in the sense
   defined in [RFC4949].  These terms include, but are not limited to,
   "attack", "authentication", "authorization", "certificate",
   "confidentiality", "credential", "encryption", "identity", "sign",
   "signature", "trust", "validate", and "verify".

   Unless otherwise noted, all the protocol parameter names and values
   are case sensitive.

2.  JOSE Authentication

   How the Client authenticates to the GS and RS are independent of each
   other.  One mechanism can be used to authenticate to the GS, and a
   different mechanism to authenticate to the RS.

   Other documents that specify other Client authentication mechanisms
   will replace this section.