OAuth Token Introspection
draft-richer-oauth-introspection-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-11-27
Replaced by draft-ietf-oauth-introspection, rfc7662
Stream (None)
Intended RFC status (None)
Formats plain text 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. Richer, Ed.
Internet-Draft                                     The MITRE Corporation
Intended status: Standards Track                       November 27, 2012
Expires: May 31, 2013

                       OAuth Token Introspection
                  draft-richer-oauth-introspection-00

Abstract

   This specification defines a method for a client or protected
   resource to query an OAuth authorization server to determine meta-
   information about an OAuth token.

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 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 31, 2013.

Copyright Notice

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

Richer                    Expires May 31, 2013                  [Page 1]
Internet-Draft               oauth-instance                November 2012

   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
   2.  Introspection Endpoint  . . . . . . . . . . . . . . . . . . . . 3
     2.1.  Introspection Request . . . . . . . . . . . . . . . . . . . 3
     2.2.  Introspection Response  . . . . . . . . . . . . . . . . . . 3
     2.3.  Non-normative Example . . . . . . . . . . . . . . . . . . . 4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 6
   6.  Normative References  . . . . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 6

Richer                    Expires May 31, 2013                  [Page 2]
Internet-Draft               oauth-instance                November 2012

1.  Introduction

   In OAuth, the contents of tokens are opaque to clients.  This means
   that the client does not need to know anything about the content or
   structure of the token itself, if there is any.  However, there is
   still a large amount of metadata that may be attached to a token,
   such as its current validity, approved scopes, and extra information
   about the authentication context in which the token was issued.

   This specification defines an Introspection Endpoint that allows the
   holder of a token to query the Authorization Server to discover the
   set of meta-information for a token.

2.  Introspection Endpoint

   The Introspection Endpoint is an OAuth 2 Endpoint that responds to
   HTTP GET and HTTP POST requests from token holders.  The endpoint
   takes a single parameter representing the token (and optionally
   further authentication) and returns a JSON document representing the
   meta information surrounding the token.

2.1.  Introspection Request

   token  the string value of the token.

   The endpoint SHOULD also require some form of authentication to
   access this endpoint, such as the Client Authentication as described
   in OAuth 2 Core Specification [RFC6749] or a separate OAuth2 Access
   Token.  The methods of managing and validating these authentication
   credentials are out of scope of this specification.
Show full document text