Token Revocation
draft-ietf-oauth-revocation-01

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Last updated 2012-10-06
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
OAuth Working Group                                  T. Lodderstedt, Ed.
Internet-Draft                                       Deutsche Telekom AG
Intended status: Standards Track                               S. Dronia
Expires: April 9, 2013
                                                           M. Scurtescu
                                                                  Google
                                                         October 6, 2012

                            Token Revocation
                     draft-ietf-oauth-revocation-01

Abstract

   This draft proposes an additional endpoint for OAuth authorization
   servers for revoking tokens.

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 April 9, 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

Lodderstedt, et al.       Expires April 9, 2013                 [Page 1]
Internet-Draft              Token Revocation                October 2012

   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
   2.  Token Revocation  . . . . . . . . . . . . . . . . . . . . . . . 3
     2.1.  Cross-Origin Support  . . . . . . . . . . . . . . . . . . . 5
   3.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

Lodderstedt, et al.       Expires April 9, 2013                 [Page 2]
Internet-Draft              Token Revocation                October 2012

1.  Introduction

   The OAuth 2.0 core specification [I-D.ietf-oauth-v2] 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 the external representation
   of an access grant issued by a resource owner to a particular client.
   A revocation request may discard the actual token as well as other
   tokens based on the same access grant and the access grant itself.

   This mechanism facilitates the following use cases:

   o  The end-user triggers revocation from within the client that sends
      the appropriate revocation request to the autorization server.
      The request causes the removal of the client's access grant the
      particular token refers to.  From the end-user's perspective, this
      looks like a "logout" or "reset" function.  This use case makes it
      even more comfortable to the end-user to revoke his access grant
      immediately via the client.

   o  In contrast to revocation by a client, the authorization server
      (or a related entity) may offer its end-users a self-care portal
      to delete access grants given to clients independent of any token
      storing devices.  Such a portal offers the possibility to an end-
Show full document text