OAuth 2.0 Token Revocation
draft-ietf-oauth-revocation-09

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Last updated 2013-05-30 (latest revision 2013-05-19)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Stephen Farrell
IESG note Hannes Tschofenig (hannes.tschofenig@gmx.net) is the document shepherd.
Send notices to oauth-chairs@tools.ietf.org, draft-ietf-oauth-revocation@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
OAuth Working Group                                  T. Lodderstedt, Ed.
Internet-Draft                                       Deutsche Telekom AG
Intended status: Standards Track                               S. Dronia
Expires: November 20, 2013                                  M. Scurtescu
                                                                  Google
                                                            May 19, 2013

                       OAuth 2.0 Token Revocation
                     draft-ietf-oauth-revocation-09

Abstract

   This document proposes an additional endpoint for OAuth authorization
   servers, which allows clients to notify the authorization server that
   a previously obtained refresh or access token is no longer needed.
   This allows the authorization server to cleanup security credentials.
   A revocation request will invalidate the actual token and, if
   applicable, other tokens based on the same authorization grant.

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 November 20, 2013.

Lodderstedt, et al.    Expires November 20, 2013                [Page 1]
Internet-Draft              Token Revocation                    May 2013

Copyright Notice

   Copyright (c) 2013 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Token Revocation  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Revocation Request  . . . . . . . . . . . . . . . . . . .   3
     2.2.  Revocation Response . . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Error Response  . . . . . . . . . . . . . . . . . . .   5
     2.3.  Cross-Origin Support  . . . . . . . . . . . . . . . . . .   5
   3.  Implementation Note . . . . . . . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  OAuth Extensions Error Registration . . . . . . . . . . .   7
       4.1.1.  The "unsupported_token_type" Error Value  . . . . . .   7
       4.1.2.  OAuth Token Type Hint Registry  . . . . . . . . . . .   7
         4.1.2.1.  Registration Template . . . . . . . . . . . . . .   8
         4.1.2.2.  Initial Registry Contents . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The OAuth 2.0 core specification [RFC6749] defines several ways for a
   client to obtain refresh and access tokens.  This specification
   supplements the core specification with a mechanism to revoke both
   types of tokens.  A token is a string representing an authorization
   grant issued by the resource owner to the client.  A revocation
   request will invalidate the actual token and, if applicable, other
   tokens based on the same authorization grant and the authorization
   grant itself.
Show full document text