Stateless Client Identifier for OAuth 2
draft-bradley-oauth-stateless-client-id-05

Document Type Active Internet-Draft (individual)
Last updated 2018-01-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    J. Bradley, Ed.
Internet-Draft                                                    Yubico
Intended status: Experimental                                  J. Richer
Expires: July 11, 2018                                  January 07, 2018

                Stateless Client Identifier for OAuth 2
               draft-bradley-oauth-stateless-client-id-05

Abstract

   This draft provides a method for communicating information about an
   OAuth client through its client identifier allowing for fully
   stateless operation.

Requirements Language

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

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 July 11, 2018.

Copyright Notice

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

Bradley & Richer          Expires July 11, 2018                 [Page 1]
Internet-Draft              Abbreviated-Title               January 2018

   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.  Stateless Client Identifier . . . . . . . . . . . . . . . . .   2
   3.  Validating the Stateless Client Identifier  . . . . . . . . .   3
   4.  Obtaining a Stateless Client Identifier . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Appendix A.  Document History . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   In the OAuth 2.0 Authorization protocol, the Client must provide a
   Client Identifier that the Authorization Server recognizes.
   Additionally, an Autorization Server needs to know about a client's
   details, such as its name and redirect URIs.  Traditionally, this is
   handled through a registration process, which may be either manual or
   automated, where the authorization server maintains a stateful
   relationship between the Client Identifier and its associated
   metadata.  This draft proposes a mechanism whereby the essential
   metadata can be encoded into the Client Identifier itself, signed by
   the issuer, and validated by the authorization server, thus allowing
   the authorization server to be stateless in regard to client
   information.

2.  Stateless Client Identifier

   The stateless client identifier consists of a JWT [RFC7519],
   optionally signed with JWS [RFC7515], whose payload contains claims
   as defined here.

   iss  REQUIRED.  URL identifying the party that issued this client
      identifier.

   sub  REQUIRED.  Identifier of the client, locally unique to the
      issuer.

   iat  OPTIONAL.  Timestamp of when this client identifier was issued.

   exp  OPTIONAL.  Timestamp of when this client identifier will expire.

Bradley & Richer          Expires July 11, 2018                 [Page 2]
Internet-Draft              Abbreviated-Title               January 2018

   kid  RECOMMENDED if signed.  Identifier of the key used to sign this
      client identifier at the issuer.

   reg  REQUIRED.  JSON Object containing a set of metadata claims of
      client information such as its redirect URIs, display name, and
      other items as defined in Dynamic Client Registration [RFC7591]
      and its extensions.

   The issuer SHOULD sign the JWT with JWS in such a way that the
Show full document text