A SASL and GSS-API Mechanism for OAuth
draft-ietf-kitten-sasl-oauth-02

The information below is for an old version of the document
Document Type Active Internet-Draft (kitten WG)
Last updated 2012-08-03
Replaces draft-mills-kitten-sasl-oauth
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
KITTEN                                                          W. Mills
Internet-Draft                                               Yahoo! Inc.
Intended status: Standards Track                            T. Showalter
Expires: February 5, 2013
                                                           H. Tschofenig
                                                  Nokia Siemens Networks
                                                          August 4, 2012

                 A SASL and GSS-API Mechanism for OAuth
                    draft-ietf-kitten-sasl-oauth-02

Abstract

   OAuth enables a third-party application to obtain limited access to a
   protected resource, either on behalf of a resource owner by
   orchestrating an approval interaction, or by allowing the third-party
   application to obtain access on its own behalf.

   This document defines how an application client uses OAuth over the
   Simple Authentication and Security Layer (SASL) or the Generic
   Security Service Application Program Interface (GSS-API) to access a
   protected resource at a resource serve.  Thereby, it enables schemes
   defined within the OAuth framework for non-HTTP-based application
   protocols.

   Clients typically store the user's long term credential.  This does,
   however, lead to significant security vulnerabilities, for example,
   when such a credential leaks.  A significant benefit of OAuth for
   usage in those clients is that the password is replaced by a token.
   Tokens typically provided limited access rights and can be managed
   and revoked separately from the user's long-term credential
   (password).

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."

Mills, et al.           Expires February 5, 2013                [Page 1]
Internet-Draft     A SASL/GSS-API Mechanism for OAuth        August 2012

   This Internet-Draft will expire on February 5, 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
   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.

Mills, et al.           Expires February 5, 2013                [Page 2]
Internet-Draft     A SASL/GSS-API Mechanism for OAuth        August 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  7
   3.  OAuth SASL Mechanism Specification . . . . . . . . . . . . . .  8
     3.1.  Initial Client Response  . . . . . . . . . . . . . . . . .  8
       3.1.1.  Reserved Key/Values in OAUTH . . . . . . . . . . . . .  9
     3.2.  Server's Response  . . . . . . . . . . . . . . . . . . . .  9
       3.2.1.  Mapping to SASL Identities . . . . . . . . . . . . . .  9
       3.2.2.  Server response to failed authentication.  . . . . . . 10
     3.3.  Use of Signature Type Authorization  . . . . . . . . . . . 10
     3.4.  Channel Binding  . . . . . . . . . . . . . . . . . . . . . 11
   4.  GSS-API OAuth Mechanism Specification  . . . . . . . . . . . . 13
   5.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     5.1.  Successful Bearer Token Exchange . . . . . . . . . . . . . 14
     5.2.  MAC Authentication with Channel Binding  . . . . . . . . . 14
     5.3.  Failed Exchange  . . . . . . . . . . . . . . . . . . . . . 15
     5.4.  Failed Channel Binding . . . . . . . . . . . . . . . . . . 16
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 18
     7.1.  SASL Registration  . . . . . . . . . . . . . . . . . . . . 18
     7.2.  GSS-API Registration . . . . . . . . . . . . . . . . . . . 18
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 19
Show full document text