Resource Indicators for OAuth 2.0
draft-campbell-oauth-resource-indicators-02

Document Type Active Internet-Draft (individual)
Last updated 2016-11-14
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)
OAuth Working Group                                          B. Campbell
Internet-Draft                                                J. Bradley
Intended status: Standards Track                           Ping Identity
Expires: May 19, 2017                                      H. Tschofenig
                                                                     ARM
                                                       November 15, 2016

                   Resource Indicators for OAuth 2.0
              draft-campbell-oauth-resource-indicators-02

Abstract

   This straw-man specification defines an extension to The OAuth 2.0
   Authorization Framework that enables the client and authorization
   server to more explicitly to communicate about the protected
   resource(s) to be accessed.

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 May 19, 2017.

Copyright Notice

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

Campbell, et al.          Expires May 19, 2017                  [Page 1]
Internet-Draft          OAuth Resource Indicators          November 2016

   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 Notation and Conventions . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Resource Parameter  . . . . . . . . . . . . . . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  OAuth Parameters Registration . . . . . . . . . . . . . .   5
       3.1.1.  Registry Contents . . . . . . . . . . . . . . . . . .   5
     3.2.  OAuth Extensions Error Registration . . . . . . . . . . .   6
       3.2.1.  Registry Contents . . . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   8
   Appendix B.  Document History . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Several years of deployment and implementation experience with OAuth
   2.0 [RFC6749] has uncovered a need, in some circumstances, for the
   client to explicitly signal to the authorization sever where it
   intends to use the access token it is requesting.

   Knowing which resource server will process the access token enables
   the authorization server to construct the token as necessary for that
   entity.  Properly encrypting the token (or content within the token)
   to a particular resource server, for example, requires knowing which
   resource server will receive and decrypt the token.  Furthermore,
   various resource servers oftentimes have different requirements with
   respect to the data contained in, or referenced by, the token and
   knowing the resource server where the client intends to use the s
   token allows the the authorization server to mint the token
   accordingly.

   Specific knowledge of the intended recipient(s) of the access token
   also helps facilitate improved security characteristics of the token
   itself.  Bearer tokens, currently the only defined type of OAuth
   access token, allow any party in possession of a token to get access
   to the associated resources.  To prevent misuse, two important
Show full document text