Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants
draft-ietf-oauth-assertions-15

OAuth Working Group                                          B. Campbell
Internet-Draft                                             Ping Identity
Intended status: Standards Track                            C. Mortimore
Expires: September 20, 2014                                   Salesforce
                                                                M. Jones
                                                               Y. Goland
                                                               Microsoft
                                                          March 19, 2014

      Assertion Framework for OAuth 2.0 Client Authentication and
                          Authorization Grants
                     draft-ietf-oauth-assertions-15

Abstract

   This specification provides a framework for the use of assertions
   with OAuth 2.0 in the form of a new client authentication mechanism
   and a new authorization grant type.  Mechanisms are specified for
   transporting assertions during interactions with a token endpoint, as
   well as general processing rules.

   The intent of this specification is to provide a common framework for
   OAuth 2.0 to interwork with other identity systems using assertions,
   and to provide alternative client authentication mechanisms.

   Note that this specification only defines abstract message flows and
   processing rules.  In order to be implementable, companion
   specifications are necessary to provide the corresponding concrete
   instantiations.

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 September 20, 2014.

Campbell, et al.       Expires September 20, 2014               [Page 1]
Internet-Draft          OAuth Assertion Framework             March 2014

Copyright Notice

   Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Notational Conventions . . . . . . . . . . . . . . . . . . . .  5
   3.  Framework  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Transporting Assertions  . . . . . . . . . . . . . . . . . . .  8
     4.1.  Using Assertions as Authorization Grants . . . . . . . . .  8
       4.1.1.  Error Responses  . . . . . . . . . . . . . . . . . . .  9
     4.2.  Using Assertions for Client Authentication . . . . . . . .  9
       4.2.1.  Error Responses  . . . . . . . . . . . . . . . . . . . 10
   5.  Assertion Content and Processing . . . . . . . . . . . . . . . 11
     5.1.  Assertion Metamodel  . . . . . . . . . . . . . . . . . . . 11
     5.2.  General Assertion Format and Processing Rules  . . . . . . 12
   6.  Common Scenarios . . . . . . . . . . . . . . . . . . . . . . . 13
     6.1.  Client Authentication  . . . . . . . . . . . . . . . . . . 13
     6.2.  Client Acting on Behalf of Itself  . . . . . . . . . . . . 14
     6.3.  Client Acting on Behalf of a User  . . . . . . . . . . . . 14
       6.3.1.  Client Acting on Behalf of an Anonymous User . . . . . 14
   7.  Interoperability Considerations  . . . . . . . . . . . . . . . 15
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
     8.1.  Forged Assertion . . . . . . . . . . . . . . . . . . . . . 16
     8.2.  Stolen Assertion . . . . . . . . . . . . . . . . . . . . . 16
     8.3.  Unauthorized Disclosure of Personal Information  . . . . . 17
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 18
     9.1.  assertion Parameter Registration . . . . . . . . . . . . . 18
     9.2.  client_assertion Parameter Registration  . . . . . . . . . 18