Raw-Public-Key and Pre-Shared-Key as OAuth client credentials
draft-erdtman-oauth-rpcc-00

Document Type Active Internet-Draft (individual)
Last updated 2017-11-21
Replaces draft-erdtman-ace-rpcc
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)
Web Authorization Protocol                                      L. Seitz
Internet-Draft                                                 RISE SICS
Intended status: Informational                                S. Erdtman
Expires: May 24, 2018                                         Spotify AB
                                                               M. Tiloca
                                                            RISE SICS AB
                                                       November 20, 2017

     Raw-Public-Key and Pre-Shared-Key as OAuth client credentials
                      draft-erdtman-oauth-rpcc-00

Abstract

   This document describes Transport Layer Security (TLS) authentication
   using Raw-Public-Key and Pre-Shared-Key as new mechanisms for OAuth
   client authentication.  Although defined for TLS the mechanisms are
   equally applicable for DTLS.

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 24, 2018.

Copyright Notice

   Copyright (c) 2017 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, et al.             Expires May 24, 2018                  [Page 1]
Internet-Draft          draft-erdtman-oauth-rpcc           November 2017

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Pre-Shared-Key for Client Authentication  . . . . . . . . . .   2
   3.  Raw-Public-Key for Client Authentication  . . . . . . . . . .   3
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Token Endpoint Authentication Method Registration . . . .   4
       5.1.1.  Registry Contents . . . . . . . . . . . . . . . . . .   4
       5.1.2.  Registry Contents . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   This document describes Transport Layer Security (TLS) authentication
   using Raw-Public-Key and Pre-Shared-Key as the mechanism for OAuth
   client authentication.  Examples of endpoint requiring client
   authentication are token and introspection.

   The OAuth 2.0 Authorization Framework [RFC6749] defines a shared
   secret method of client authentication but also allows for the
   definition and use of additional client authentication mechanisms
   when interacting with the authorization server's token endpoint.
   This document describes two additional mechanisms of client
   authentication utilizing Raw-Public-Key [RFC7250] and Pre-Shared-Key
   TLS [RFC4279], which provide better security characteristics than
   shared secrets.

1.1.  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].

2.  Pre-Shared-Key for Client Authentication

   The following section defines, as an extension of OAuth 2.0,
   Section 2.3 [RFC6749], using Pre-Shared-Key with TLS [RFC4279] to
   authenticate the client.  This method is registered as
   'tls_client_psk' in "OAuth Token Endpoint Authentication Methods"

Seitz, et al.             Expires May 24, 2018                  [Page 2]
Internet-Draft          draft-erdtman-oauth-rpcc           November 2017

   registry.  If this method is to be used, the client and the
Show full document text