The OAuth 2.0 Authorization Framework
draft-ietf-oauth-v2-30

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Last updated 2012-07-15
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd Barry Leiba
Shepherd write-up Show (last changed 2011-09-22)
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Stephen Farrell
Send notices to oauth-chairs@tools.ietf.org, draft-ietf-oauth-v2@tools.ietf.org
OAuth Working Group                                        D. Hardt, Ed.
Internet-Draft                                                 Microsoft
Obsoletes: 5849 (if approved)                                D. Recordon
Intended status: Standards Track                                Facebook
Expires: January 16, 2013                                  July 15, 2012

                 The OAuth 2.0 Authorization Framework
                         draft-ietf-oauth-v2-30

Abstract

   The OAuth 2.0 authorization framework enables a third-party
   application to obtain limited access to an HTTP service, either on
   behalf of a resource owner by orchestrating an approval interaction
   between the resource owner and the HTTP service, or by allowing the
   third-party application to obtain access on its own behalf.  This
   specification replaces and obsoletes the OAuth 1.0 protocol described
   in RFC 5849.

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 January 16, 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
   to this document.  Code Components extracted from this document must

Hardt & Recordon        Expires January 16, 2013                [Page 1]
Internet-Draft                  OAuth 2.0                      July 2012

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.   Roles . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     1.2.   Protocol Flow . . . . . . . . . . . . . . . . . . . . . .  7
     1.3.   Authorization Grant . . . . . . . . . . . . . . . . . . .  8
       1.3.1.  Authorization Code . . . . . . . . . . . . . . . . . .  8
       1.3.2.  Implicit . . . . . . . . . . . . . . . . . . . . . . .  8
       1.3.3.  Resource Owner Password Credentials  . . . . . . . . .  9
       1.3.4.  Client Credentials . . . . . . . . . . . . . . . . . .  9
     1.4.   Access Token  . . . . . . . . . . . . . . . . . . . . . .  9
     1.5.   Refresh Token . . . . . . . . . . . . . . . . . . . . . . 10
     1.6.   TLS Version . . . . . . . . . . . . . . . . . . . . . . . 12
     1.7.   HTTP Redirections . . . . . . . . . . . . . . . . . . . . 12
     1.8.   Interoperability  . . . . . . . . . . . . . . . . . . . . 12
     1.9.   Notational Conventions  . . . . . . . . . . . . . . . . . 12
   2.  Client Registration  . . . . . . . . . . . . . . . . . . . . . 13
     2.1.   Client Types  . . . . . . . . . . . . . . . . . . . . . . 13
     2.2.   Client Identifier . . . . . . . . . . . . . . . . . . . . 15
     2.3.   Client Authentication . . . . . . . . . . . . . . . . . . 15
       2.3.1.  Client Password  . . . . . . . . . . . . . . . . . . . 15
       2.3.2.  Other Authentication Methods . . . . . . . . . . . . . 17
     2.4.   Unregistered Clients  . . . . . . . . . . . . . . . . . . 17
   3.  Protocol Endpoints . . . . . . . . . . . . . . . . . . . . . . 17
     3.1.   Authorization Endpoint  . . . . . . . . . . . . . . . . . 17
       3.1.1.  Response Type  . . . . . . . . . . . . . . . . . . . . 18
       3.1.2.  Redirection Endpoint . . . . . . . . . . . . . . . . . 18
     3.2.   Token Endpoint  . . . . . . . . . . . . . . . . . . . . . 21
       3.2.1.  Client Authentication  . . . . . . . . . . . . . . . . 21
     3.3.   Access Token Scope  . . . . . . . . . . . . . . . . . . . 22
   4.  Obtaining Authorization  . . . . . . . . . . . . . . . . . . . 22
     4.1.   Authorization Code Grant  . . . . . . . . . . . . . . . . 23
       4.1.1.  Authorization Request  . . . . . . . . . . . . . . . . 24
       4.1.2.  Authorization Response . . . . . . . . . . . . . . . . 25
Show full document text