OAuth 2.0 Token Binding
draft-ietf-oauth-token-binding-03

Document Type Active Internet-Draft (oauth WG)
Last updated 2017-03-27
Replaces draft-jones-oauth-token-binding, draft-campbell-oauth-tbpkce
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
OAuth Working Group                                             M. Jones
Internet-Draft                                                 Microsoft
Intended status: Standards Track                              J. Bradley
Expires: September 28, 2017                                  B. Campbell
                                                           Ping Identity
                                                              W. Denniss
                                                                  Google
                                                          March 27, 2017

                        OAuth 2.0 Token Binding
                   draft-ietf-oauth-token-binding-03

Abstract

   This specification enables OAuth 2.0 implementations to apply Token
   Binding to Access Tokens, Authorization Codes, and Refresh Tokens.
   This cryptographically binds these tokens to a client's Token Binding
   key pair, possession of which is proven on the TLS connections over
   which the tokens are intended to be used.  This use of Token Binding
   protects these tokens from man-in-the-middle and token export and
   replay attacks.

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 http://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 September 28, 2017.

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
   (http://trustee.ietf.org/license-info) in effect on the date of

Jones, et al.          Expires September 28, 2017               [Page 1]
Internet-Draft           OAuth 2.0 Token Binding              March 2017

   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.  Requirements Notation and Conventions . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Token Binding for Refresh Tokens  . . . . . . . . . . . . . .   3
     2.1.  Example Token Binding for Refresh Tokens  . . . . . . . .   4
   3.  Token Binding for Access Tokens . . . . . . . . . . . . . . .   6
     3.1.  Access Tokens Issued from the Authorization Endpoint  . .   7
       3.1.1.  Example Access Token Issued from the Authorization
               Endpoint  . . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Access Tokens Issued from the Token Endpoint  . . . . . .   9
       3.2.1.  Example Access Token Issued from the Token Endpoint .   9
     3.3.  Protected Resource Token Binding Validation . . . . . . .  11
       3.3.1.  Example Protected Resource Request  . . . . . . . . .  11
     3.4.  Representing Token Binding in JWT Access Tokens . . . . .  11
   4.  Token Binding for Authorization Codes . . . . . . . . . . . .  12
     4.1.  Native Application Clients  . . . . . . . . . . . . . . .  12
       4.1.1.  Code Challenge  . . . . . . . . . . . . . . . . . . .  13
         4.1.1.1.  Example Code Challenge  . . . . . . . . . . . . .  13
       4.1.2.  Code Verifier . . . . . . . . . . . . . . . . . . . .  14
         4.1.2.1.  Example Code Verifier . . . . . . . . . . . . . .  14
     4.2.  Web Server Clients  . . . . . . . . . . . . . . . . . . .  15
       4.2.1.  Code Challenge  . . . . . . . . . . . . . . . . . . .  15
         4.2.1.1.  Example Code Challenge  . . . . . . . . . . . . .  16
       4.2.2.  Code Verifier . . . . . . . . . . . . . . . . . . . .  16
         4.2.2.1.  Example Code Verifier . . . . . . . . . . . . . .  17
   5.  Phasing in Token Binding and Preventing Downgrade Attacks . .  18
   6.  Token Binding Metadata  . . . . . . . . . . . . . . . . . . .  18
     6.1.  Token Binding Client Metadata . . . . . . . . . . . . . .  18
     6.2.  Token Binding Authorization Server Metadata . . . . . . .  19
Show full document text