draft-ietf-oauth-saml2-bearer-10.txt   draft-ietf-oauth-saml2-bearer-11.txt 
B. Campbell, Ed. B. Campbell, Ed.
Internet-Draft Ping Identity Corp. Internet-Draft Ping Identity
Intended status: Standards Track C. Mortimore Intended status: Standards Track C. Mortimore
Expires: July 4, 2012 Salesforce.com Expires: October 28, 2012 Salesforce
Jan 2012 April 26, 2012
SAML 2.0 Bearer Assertion Profiles for OAuth 2.0 SAML 2.0 Bearer Assertion Profiles for OAuth 2.0
draft-ietf-oauth-saml2-bearer-10 draft-ietf-oauth-saml2-bearer-11
Abstract Abstract
This specification defines the use of a SAML 2.0 Bearer Assertion as This specification defines the use of a SAML 2.0 Bearer Assertion as
means for requesting an OAuth 2.0 access token as well as for use as a means for requesting an OAuth 2.0 access token as well as for use
a means of client authentication. as a means of client authentication.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 4, 2012. This Internet-Draft will expire on October 28, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 4 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. HTTP Parameter Bindings for Transporting Assertions . . . . . 4 2. HTTP Parameter Bindings for Transporting Assertions . . . . . 4
2.1. Using SAML Assertions as Authorization Grants . . . . . . 4 2.1. Using SAML Assertions as Authorization Grants . . . . . . 4
2.2. Using SAML Assertions for Client Authentication . . . . . 4 2.2. Using SAML Assertions for Client Authentication . . . . . 5
3. Assertion Format and Processing Requirements . . . . . . . . . 5 3. Assertion Format and Processing Requirements . . . . . . . . . 5
3.1. Authorization Grant Processing . . . . . . . . . . . . . . 7 3.1. Authorization Grant Processing . . . . . . . . . . . . . . 7
3.2. Client Authentication Processing . . . . . . . . . . . . . 8 3.2. Client Authentication Processing . . . . . . . . . . . . . 8
4. Authorization Grant Example (non-normative) . . . . . . . . . 8 4. Authorization Grant Example . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6.1. Sub-Namespace Registration of 6.1. Sub-Namespace Registration of
urn:ietf:params:oauth:grant-type:saml2-bearer . . . . . . 10 urn:ietf:params:oauth:grant-type:saml2-bearer . . . . . . 10
6.2. Sub-Namespace Registration of 6.2. Sub-Namespace Registration of
urn:ietf:params:oauth:client-assertion-type:saml2-bearer . 10 urn:ietf:params:oauth:client-assertion-type:saml2-bearer . 11
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Appendix B. Document History . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 7.2. Informative References . . . . . . . . . . . . . . . . . . 12
7.1. Normative References . . . . . . . . . . . . . . . . . . . 15 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . . 15 Appendix B. Document History . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
The Security Assertion Markup Language (SAML) 2.0 The Security Assertion Markup Language (SAML) 2.0
[OASIS.saml-core-2.0-os] is an XML-based framework that allows [OASIS.saml-core-2.0-os] is an XML-based framework that allows
identity and security information to be shared across security identity and security information to be shared across security
domains. The SAML specification, while primarily targeted at domains. The SAML specification, while primarily targeted at
providing cross domain Web browser single sign-on, was also designed providing cross domain Web browser single sign-on, was also designed
to be modular and extensible to facilitate use in other contexts. to be modular and extensible to facilitate use in other contexts.
The Assertion, an XML security token, is a fundamental construct of The Assertion, an XML security token, is a fundamental construct of
SAML that is often adopted for use in other protocols and SAML that is often adopted for use in other protocols and
specifications. An Assertion is generally issued by an identity specifications. An Assertion is generally issued by an identity
provider and consumed by a service provider who relies on its content provider and consumed by a service provider who relies on its content
to identify the Assertion's subject for security related purposes. to identify the Assertion's subject for security related purposes.
The OAuth 2.0 Authorization Protocol [I-D.ietf.oauth-v2] provides a The OAuth 2.0 Authorization Protocol [I-D.ietf-oauth-v2] provides a
method for making authenticated HTTP requests to a resource using an method for making authenticated HTTP requests to a resource using an
access token. Access tokens are issued to third-party clients by an access token. Access tokens are issued to third-party clients by an
authorization server (AS) with the (sometimes implicit) approval of authorization server (AS) with the (sometimes implicit) approval of
the resource owner. In OAuth, an authorization grant is an abstract the resource owner. In OAuth, an authorization grant is an abstract
term used to describe intermediate credentials that represent the term used to describe intermediate credentials that represent the
resource owner authorization. An authorization grant is used by the resource owner authorization. An authorization grant is used by the
client to obtain an access token. Several authorization grant types client to obtain an access token. Several authorization grant types
are defined to support a wide range of client types and user are defined to support a wide range of client types and user
experiences. OAuth also allows for the definition of new extension experiences. OAuth also allows for the definition of new extension
grant types to support additional clients or to provide a bridge grant types to support additional clients or to provide a bridge
between OAuth and other trust frameworks. Finally, OAuth allows the between OAuth and other trust frameworks. Finally, OAuth allows the
definition of additional authentication mechanisms to be used by definition of additional authentication mechanisms to be used by
clients when interacting with the authorization server. clients when interacting with the authorization server.
The OAuth 2.0 Assertion Profile [I-D.ietf.oauth-assertions] is an The OAuth 2.0 Assertion Profile [I-D.ietf-oauth-assertions] is an
abstract extension to OAuth 2.0 that provides a general framework for abstract extension to OAuth 2.0 that provides a general framework for
the use of assertions as client credentials and/or authorization the use of Assertions as client credentials and/or authorization
grants with OAuth 2.0. This specification profiles the OAuth 2.0 grants with OAuth 2.0. This specification profiles the OAuth 2.0
Assertion Profile [I-D.ietf.oauth-assertions] to define an extension Assertion Profile [I-D.ietf-oauth-assertions] to define an extension
grant type that uses a SAML 2.0 Bearer Assertion to request an OAuth grant type that uses a SAML 2.0 Bearer Assertion to request an OAuth
2.0 access token as well as for use as client credentials. The 2.0 access token as well as for use as client credentials. The
format and processing rules for the SAML Assertion defined in this format and processing rules for the SAML Assertion defined in this
specification are intentionally similar, though not identical, to specification are intentionally similar, though not identical, to
those in the Web Browser SSO Profile defined in SAML Profiles those in the Web Browser SSO Profile defined in SAML Profiles
[OASIS.saml-profiles-2.0-os]. This specification is reusing, to the [OASIS.saml-profiles-2.0-os]. This specification is reusing, to the
extent reasonable, concepts and patterns from that well-established extent reasonable, concepts and patterns from that well-established
Profile. Profile.
This document defines how a SAML Assertion can be used to request an This document defines how a SAML Assertion can be used to request an
skipping to change at page 4, line 23 skipping to change at page 4, line 23
1.1. Notational Conventions 1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Unless otherwise noted, all the protocol parameter names and values Unless otherwise noted, all the protocol parameter names and values
are case sensitive. are case sensitive.
1.2. Terminology
All terms are as defined in The OAuth 2.0 Authorization Protocol
[I-D.ietf-oauth-v2], OAuth 2.0 Assertion Profile
[I-D.ietf-oauth-assertions], and Security Assertion Markup Language
(SAML) 2.0 [OASIS.saml-core-2.0-os].
2. HTTP Parameter Bindings for Transporting Assertions 2. HTTP Parameter Bindings for Transporting Assertions
The OAuth 2.0 Assertion Profile [I-D.ietf.oauth-assertions] defines The OAuth 2.0 Assertion Profile [I-D.ietf-oauth-assertions] defines
generic HTTP parameters for transporting assertions during generic HTTP parameters for transporting Assertions during
interactions with a token endpoint. This section defines the values interactions with a token endpoint. This section defines the values
of those parameters for use with SAML 2.0 Bearer Assertions. of those parameters for use with SAML 2.0 Bearer Assertions.
2.1. Using SAML Assertions as Authorization Grants 2.1. Using SAML Assertions as Authorization Grants
To use a SAML Bearer Assertion as an authorization grant, use the To use a SAML Bearer Assertion as an authorization grant, use the
following parameter values and encodings. following parameter values and encodings.
The value of "grant_type" parameter MUST be The value of the "grant_type" parameter MUST be
"urn:ietf:params:oauth:grant-type:saml2-bearer" "urn:ietf:params:oauth:grant-type:saml2-bearer".
The value of the "assertion" parameter MUST contain a single SAML 2.0 The value of the "assertion" parameter MUST contain a single SAML 2.0
Assertion. The SAML Assertion XML data MUST be encoded using Assertion. The SAML Assertion XML data MUST be encoded using
base64url, where the encoding adheres to the definition in Section 5 base64url, where the encoding adheres to the definition in Section 5
of RFC4648 [RFC4648] and where the padding bits are set to zero. To of RFC4648 [RFC4648] and where the padding bits are set to zero. To
avoid the need for subsequent encoding steps (by "application/ avoid the need for subsequent encoding steps (by "application/
x-www-form-urlencoded" [W3C.REC-html401-19991224], for example), the x-www-form-urlencoded" [W3C.REC-html401-19991224], for example), the
base64url encoded data SHOULD NOT be line wrapped and pad characters base64url encoded data SHOULD NOT be line wrapped and pad characters
("=") SHOULD NOT be included. ("=") SHOULD NOT be included.
2.2. Using SAML Assertions for Client Authentication 2.2. Using SAML Assertions for Client Authentication
To use a SAML Bearer Assertion for client authentication grant, use To use a SAML Bearer Assertion for client authentication grant, use
the following parameter values and encodings. the following parameter values and encodings.
The value of "client_assertion_type" parameter MUST be The value of the "client_assertion_type" parameter MUST be
"urn:ietf:params:oauth:client-assertion-type:saml2-bearer" "urn:ietf:params:oauth:client-assertion-type:saml2-bearer".
The value of the "client_assertion" parameter MUST contain a single The value of the "client_assertion" parameter MUST contain a single
SAML 2.0 Assertion. The SAML Assertion XML data MUST be encoded SAML 2.0 Assertion. The SAML Assertion XML data MUST be encoded
using base64url, where the encoding adheres to the definition in using base64url, where the encoding adheres to the definition in
Section 5 of RFC4648 [RFC4648] and where the padding bits are set to Section 5 of RFC4648 [RFC4648] and where the padding bits are set to
zero. To avoid the need for subsequent encoding steps (by zero. To avoid the need for subsequent encoding steps (by
"application/x-www-form-urlencoded" [W3C.REC-html401-19991224], for "application/x-www-form-urlencoded" [W3C.REC-html401-19991224], for
example), the base64url encoded data SHOULD NOT be line wrapped and example), the base64url encoded data SHOULD NOT be line wrapped and
pad characters ("=") SHOULD NOT be included. pad characters ("=") SHOULD NOT be included.
3. Assertion Format and Processing Requirements 3. Assertion Format and Processing Requirements
In order to issue an access token response as described in The OAuth In order to issue an access token response as described in The OAuth
2.0 Authorization Protocol [I-D.ietf.oauth-v2] or to rely on an 2.0 Authorization Protocol [I-D.ietf-oauth-v2] or to rely on an
assertion for client authentication, the authorization server MUST Assertion for client authentication, the authorization server MUST
validate the Assertion according to the criteria below. Application validate the Assertion according to the criteria below. Application
of additional restrictions and policy are at the discretion of the of additional restrictions and policy are at the discretion of the
authorization server. authorization server.
o The Assertion's <Issuer> element MUST contain a unique identifier o The Assertion's <Issuer> element MUST contain a unique identifier
for the entity that issued the Assertion. for the entity that issued the Assertion.
o The Assertion MUST contain <Conditions> element with an o The Assertion MUST contain <Conditions> element with an
<AudienceRestriction> element with an <Audience> element <AudienceRestriction> element with an <Audience> element
containing a URI reference that identifies the authorization containing a URI reference that identifies the authorization
server, or the service provider SAML entity of its controlling server, or the service provider SAML entity of its controlling
domain, as an intended audience. The token endpoint URL of the domain, as an intended audience. The token endpoint URL of the
authorization server MAY be used as an acceptable value for an authorization server MAY be used as an acceptable value for an
<Audience> element. The authorization server MUST verify that it <Audience> element. The authorization server MUST verify that it
is an intended audience for the Assertion. is an intended audience for the Assertion.
o The Assertion MUST contain a <Subject> element. The subject MAY o The Assertion MUST contain a <Subject> element. The subject MAY
identify the resource owner for whom the access token is being identify the resource owner for whom the access token is being
requested. For client authentication, the Subject MUST be the requested. For client authentication, the Subject MUST be the
client_id of the OAuth client. When using assertions as an "client_id" of the OAuth client. When using an Assertion as an
authorization grant, the Subject SHOULD identify an authorized authorization grant, the Subject SHOULD identify an authorized
accessor for whom the access token is being requested (typically accessor for whom the access token is being requested (typically
the resource owner, or an authorized delegate). Additional the resource owner, or an authorized delegate). Additional
information identifying the subject/principal of the transaction information identifying the subject/principal of the transaction
MAY be included in an <AttributeStatement>. MAY be included in an <AttributeStatement>.
o The Assertion MUST have an expiry that limits the time window o The Assertion MUST have an expiry that limits the time window
during which it can be used. The expiry can be expressed either during which it can be used. The expiry can be expressed either
as the NotOnOrAfter attribute of the <Conditions> element or as as the NotOnOrAfter attribute of the <Conditions> element or as
the NotOnOrAfter attribute of a suitable <SubjectConfirmationData> the NotOnOrAfter attribute of a suitable <SubjectConfirmationData>
skipping to change at page 6, line 27 skipping to change at page 6, line 35
of the authorization server. The authorization server MUST verify of the authorization server. The authorization server MUST verify
that the value of the Recipient attribute matches the token that the value of the Recipient attribute matches the token
endpoint URL (or an acceptable alias) to which the Assertion was endpoint URL (or an acceptable alias) to which the Assertion was
delivered. The <SubjectConfirmationData> element MUST have a delivered. The <SubjectConfirmationData> element MUST have a
NotOnOrAfter attribute that limits the window during which the NotOnOrAfter attribute that limits the window during which the
Assertion can be confirmed. The <SubjectConfirmationData> element Assertion can be confirmed. The <SubjectConfirmationData> element
MAY also contain an Address attribute limiting the client address MAY also contain an Address attribute limiting the client address
from which the Assertion can be delivered. Verification of the from which the Assertion can be delivered. Verification of the
Address is at the discretion of the authorization server. Address is at the discretion of the authorization server.
o The authorization server MUST verify that occurrences of the o The authorization server MUST verify that the NotOnOrAfter instant
NotOnOrAfter instant has not passed, subject to allowable clock has not passed, subject to allowable clock skew between systems.
skew between systems. An invalid NotOnOrAfter instant on the An invalid NotOnOrAfter instant on the <Conditions> element
<Conditions> element invalidates the entire assertion. An invalid invalidates the entire Assertion. An invalid NotOnOrAfter instant
NotOnOrAfter instant on a <SubjectConfirmationData> element only on a <SubjectConfirmationData> element only invalidates the
invalidates the individual <SubjectConfirmation>. The individual <SubjectConfirmation>. The authorization server MAY
authorization server MAY reject assertions with a NotOnOrAfter reject Assertions with a NotOnOrAfter instant that is unreasonably
instant that is unreasonably far in the future. The authorization far in the future. The authorization server MAY ensure that
server MAY ensure that Bearer Assertions are not replayed, by Bearer Assertions are not replayed, by maintaining the set of used
maintaining the set of used ID values for the length of time for ID values for the length of time for which the Assertion would be
which the Assertion would be considered valid based on the considered valid based on the applicable NotOnOrAfter instant.
applicable NotOnOrAfter instant.
o If the Assertion issuer authenticated the subject, the Assertion o If the Assertion issuer authenticated the subject, the Assertion
SHOULD contain a single <AuthnStatement> representing that SHOULD contain a single <AuthnStatement> representing that
authentication event. authentication event.
o If the Assertion was issued with the intention that the presenter o If the Assertion was issued with the intention that the presenter
act autonomously on behalf of the subject, an <AuthnStatement> act autonomously on behalf of the subject, an <AuthnStatement>
SHOULD NOT be included. The presenter SHOULD be identified in the SHOULD NOT be included. The presenter SHOULD be identified in the
<NameID> or similar element, the <SubjectConfirmation> element, or <NameID> or similar element, the <SubjectConfirmation> element, or
by other available means like [OASIS.saml-deleg-cs]. by other available means like [OASIS.saml-deleg-cs].
skipping to change at page 7, line 22 skipping to change at page 7, line 31
in all other respects per [OASIS.saml-core-2.0-os], such as (but in all other respects per [OASIS.saml-core-2.0-os], such as (but
not limited to) evaluating all content within the Conditions not limited to) evaluating all content within the Conditions
element including the NotOnOrAfter and NotBefore attributes, element including the NotOnOrAfter and NotBefore attributes,
rejecting unknown condition types, etc. rejecting unknown condition types, etc.
3.1. Authorization Grant Processing 3.1. Authorization Grant Processing
If present, the authorization server MUST also validate the client If present, the authorization server MUST also validate the client
credentials. credentials.
Authorization servers SHOULD issue access tokens with a limited
lifetime and require clients to refresh them by requesting a new
access token using the same assertion, if it is still valid, or with
a new assertion. The authorization server SHOULD NOT issue a refresh
token.
If the Assertion is not valid, or its subject confirmation If the Assertion is not valid, or its subject confirmation
requirements cannot be met, the authorization server MUST construct requirements cannot be met, the authorization server MUST construct
an error response as defined in [I-D.ietf.oauth-v2]. The value of an error response as defined in OAuth 2.0 [I-D.ietf-oauth-v2]. The
the error parameter MUST be the "invalid_grant" error code. The value of the "error" parameter MUST be the "invalid_grant" error
authorization server MAY include additional information regarding the code. The authorization server MAY include additional information
reasons the Assertion was considered invalid using the regarding the reasons the Assertion was considered invalid using the
error_description or error_uri parameters. "error_description" or "error_uri" parameters.
For example: For example:
HTTP/1.1 400 Bad Request HTTP/1.1 400 Bad Request
Content-Type: application/json Content-Type: application/json
Cache-Control: no-store Cache-Control: no-store
{ {
"error":"invalid_grant", "error":"invalid_grant",
"error_description":"Audience validation failed" "error_description":"Audience validation failed"
} }
3.2. Client Authentication Processing 3.2. Client Authentication Processing
If the client Assertion is not valid, or its subject confirmation If the client Assertion is not valid, or its subject confirmation
requirements cannot be met, the authorization server MUST construct requirements cannot be met, the authorization server MUST construct
an error response as defined in [I-D.ietf.oauth-v2]. The value of an error response as defined in OAuth 2.0 [I-D.ietf-oauth-v2]. The
the error parameter MUST be the "invalid_client" error code. The value of the "error" parameter MUST be the "invalid_client" error
authorization server MAY include additional information regarding the code. The authorization server MAY include additional information
reasons the Assertion was considered invalid using the regarding the reasons the Assertion was considered invalid using the
error_description or error_uri parameters. "error_description" or "error_uri" parameters.
4. Authorization Grant Example (non-normative) 4. Authorization Grant Example
Though non-normative, the following examples illustrate what a Though non-normative, the following examples illustrate what a
conforming Assertion and access token request would look like. conforming Assertion and access token request would look like.
Below is an example SAML 2.0 Assertion (whitespace formatting is for Below is an example SAML 2.0 Assertion (whitespace formatting is for
display purposes only): display purposes only):
<Assertion IssueInstant="2010-10-01T20:07:34.619Z" <Assertion IssueInstant="2010-10-01T20:07:34.619Z"
ID="ef1xsbZxPV2oqjd7HTLRLIBlBb7" ID="ef1xsbZxPV2oqjd7HTLRLIBlBb7"
Version="2.0" Version="2.0"
skipping to change at page 10, line 7 skipping to change at page 10, line 7
urn:oasis:names:tc:SAML:2.0:ac:classes:X509 urn:oasis:names:tc:SAML:2.0:ac:classes:X509
</AuthnContextClassRef> </AuthnContextClassRef>
</AuthnContext> </AuthnContext>
</AuthnStatement> </AuthnStatement>
</Assertion> </Assertion>
Figure 1: Example SAML 2.0 Assertion Figure 1: Example SAML 2.0 Assertion
To present the Assertion shown in the previous example as part of an To present the Assertion shown in the previous example as part of an
access token request, for example, the client might make the access token request, for example, the client might make the
following HTTPS request (line breaks are for display purposes only): following HTTPS request (with line breaks for display purposes only):
POST /token.oauth2 HTTP/1.1 POST /token.oauth2 HTTP/1.1
Host: authz.example.net Host: authz.example.net
Content-Type: application/x-www-form-urlencoded Content-Type: application/x-www-form-urlencoded
grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Asaml2- grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Asaml2-
bearer&assertion=PEFzc2VydGlvbiBJc3N1ZUluc3RhbnQ9IjIwMTEtMDU bearer&assertion=PEFzc2VydGlvbiBJc3N1ZUluc3RhbnQ9IjIwMTEtMDU
[...omitted for brevity...]aG5TdGF0ZW1lbnQ-PC9Bc3NlcnRpb24- [...omitted for brevity...]aG5TdGF0ZW1lbnQ-PC9Bc3NlcnRpb24-
Figure 2: Example Request Figure 2: Example Request
5. Security Considerations 5. Security Considerations
No additional considerations beyond those described within the OAuth No additional security considerations apply beyond those described
2.0 Protocol Framework [I-D.ietf.oauth-v2] and in the Security and within The OAuth 2.0 Authorization Protocol [I-D.ietf-oauth-v2], the
Privacy Considerations for the OASIS Security Assertion Markup OAuth 2.0 Assertion Profile [I-D.ietf-oauth-assertions], and in the
Language (SAML) V2.0 [OASIS.saml-sec-consider-2.0-os]. Security and Privacy Considerations for the OASIS Security Assertion
Markup Language (SAML) V2.0 [OASIS.saml-sec-consider-2.0-os].
6. IANA Considerations 6. IANA Considerations
6.1. Sub-Namespace Registration of 6.1. Sub-Namespace Registration of
urn:ietf:params:oauth:grant-type:saml2-bearer urn:ietf:params:oauth:grant-type:saml2-bearer
This is a request to IANA to please register the value grant- This is a request to IANA to please register the value
type:saml2-bearer in the registry urn:ietf:params:oauth established "grant-type:saml2-bearer" in the registry urn:ietf:params:oauth
in [I-D.ietf.oauth-urn-sub-ns] established in An IETF URN Sub-Namespace for OAuth
[I-D.ietf-oauth-urn-sub-ns].
o URN: urn:ietf:params:oauth:grant-type:saml2-bearer o URN: urn:ietf:params:oauth:grant-type:saml2-bearer
o Common Name: SAML 2.0 Bearer Assertion Grant Type Profile for o Common Name: SAML 2.0 Bearer Assertion Grant Type Profile for
OAuth 2.0 OAuth 2.0
o Change controller: IETF o Change controller: IETF
o Description: [[this document]] o Description: [[this document]]
6.2. Sub-Namespace Registration of 6.2. Sub-Namespace Registration of
urn:ietf:params:oauth:client-assertion-type:saml2-bearer urn:ietf:params:oauth:client-assertion-type:saml2-bearer
This is a request to IANA to please register the value client- This is a request to IANA to please register the value
assertion-type:saml2-bearer in the registry urn:ietf:params:oauth "client-assertion-type:saml2-bearer" in the registry
established in [I-D.ietf.oauth-urn-sub-ns] urn:ietf:params:oauth established in An IETF URN Sub-Namespace for
OAuth [I-D.ietf-oauth-urn-sub-ns].
o URN: urn:ietf:params:oauth:client-assertion-type:saml2-bearer o URN: urn:ietf:params:oauth:client-assertion-type:saml2-bearer
o Common Name: SAML 2.0 Bearer Assertion Profile for OAuth 2.0 o Common Name: SAML 2.0 Bearer Assertion Profile for OAuth 2.0
Client Authentication Client Authentication
o Change controller: IETF o Change controller: IETF
o Description: [[this document]] o Description: [[this document]]
Appendix A. Contributors 7. References
7.1. Normative References
[I-D.ietf-oauth-assertions]
Mortimore, C., Ed., Jones, M., Campbell, B., and Y.
Goland, "OAuth 2.0 Assertion Profile",
draft-ietf-oauth-assertions-02 (work in progress),
April 2012.
[I-D.ietf-oauth-urn-sub-ns]
Tschofenig, H., "An IETF URN Sub-Namespace for OAuth",
draft-ietf-oauth-urn-sub-ns-02 (work in progress),
January 2012.
[I-D.ietf-oauth-v2]
Hammer-Lahav, E., Recordon, D., and D. Hardt, "The OAuth
2.0 Authorization Protocol", draft-ietf-oauth-v2-25 (work
in progress), March 2012.
[OASIS.saml-core-2.0-os]
Cantor, S., Kemp, J., Philpott, R., and E. Maler,
"Assertions and Protocol for the OASIS Security Assertion
Markup Language (SAML) V2.0", OASIS Standard saml-core-
2.0-os, March 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, October 2006.
7.2. Informative References
[OASIS.saml-deleg-cs]
Cantor, S., Ed., "SAML V2.0 Condition for Delegation
Restriction", Nov 2009.
[OASIS.saml-profiles-2.0-os]
Hughes, J., Cantor, S., Hodges, J., Hirsch, F., Mishra,
P., Philpott, R., and E. Maler, "Profiles for the OASIS
Security Assertion Markup Language (SAML) V2.0", OASIS
Standard OASIS.saml-profiles-2.0-os, March 2005.
[OASIS.saml-sec-consider-2.0-os]
Hirsch, F., Philpott, R., and E. Maler, "Security and
Privacy Considerations for the OASIS Security Markup
Language (SAML) V2.0", OASIS Standard saml-sec-consider-
2.0-os, March 2005.
[W3C.REC-html401-19991224]
Hors, A., Raggett, D., and I. Jacobs, "HTML 4.01
Specification", World Wide Web Consortium
Recommendation REC-html401-19991224, December 1999,
<http://www.w3.org/TR/1999/REC-html401-19991224>.
Appendix A. Acknowledgements
The following people contributed wording and concepts to this The following people contributed wording and concepts to this
document: Paul Madsen, Patrick Harding, Peter Motykowski, Eran document: Paul Madsen, Patrick Harding, Peter Motykowski, Eran
Hammer-Lahav, Peter Saint-Andre, Ian Barnett, Eric Fazendin, Torsten Hammer, Peter Saint-Andre, Ian Barnett, Eric Fazendin, Torsten
Lodderstedt, Susan Harper, Scott Tomilson, Scott Cantor, Michael Lodderstedt, Susan Harper, Scott Tomilson, Scott Cantor, Michael B.
Jones, Hannes Tschofenig, David Waite and Mukesh Bhatnagar. Jones, Hannes Tschofenig, David Waite, Phil Hunt, and Mukesh
Bhatnagar.
Appendix B. Document History Appendix B. Document History
[[ to be removed by RFC editor before publication as an RFC ]] [[ to be removed by RFC editor before publication as an RFC ]]
draft-ietf-oauth-saml2-bearer-11
o Removed text about limited lifetime access tokens and the SHOULD
NOT on issuing refresh tokens. The text was moved to
draft-ietf-oauth-assertions-02 and somewhat modified per
http://www.ietf.org/mail-archive/web/oauth/current/msg08298.html.
o Fixed typo/missing word per
http://www.ietf.org/mail-archive/web/oauth/current/msg08733.html.
o Added Terminology section.
draft-ietf-oauth-saml2-bearer-10 draft-ietf-oauth-saml2-bearer-10
o fix a spelling mistake o fix a spelling mistake
draft-ietf-oauth-saml2-bearer-09 draft-ietf-oauth-saml2-bearer-09
o Attempt to address an ambiguity around validation requirements o Attempt to address an ambiguity around validation requirements
when the Conditions element contain a NotOnOrAfter and when the Conditions element contain a NotOnOrAfter and
SubjectConfirmation/SubjectConfirmationData does too. Basically SubjectConfirmation/SubjectConfirmationData does too. Basically
it needs to have at least one bearer SubjectConfirmation element it needs to have at least one bearer SubjectConfirmation element
skipping to change at page 12, line 4 skipping to change at page 13, line 34
have them checked. have them checked.
o clarified that AudienceRestriction is under Conditions (even o clarified that AudienceRestriction is under Conditions (even
though it's implied by schema) though it's implied by schema)
o fix a typo o fix a typo
draft-ietf-oauth-saml2-bearer-08 draft-ietf-oauth-saml2-bearer-08
o fix some typos o fix some typos
draft-ietf-oauth-saml2-bearer-07
o update reference from draft-campbell-oauth-urn-sub-ns to o update reference from draft-campbell-oauth-urn-sub-ns to
draft-ietf-oauth-urn-sub-ns draft-ietf-oauth-urn-sub-ns
o Updated to reference draft-ietf-oauth-v2-20 o Updated to reference draft-ietf-oauth-v2-20
draft-ietf-oauth-saml2-bearer-06 draft-ietf-oauth-saml2-bearer-06
o Fix three typos NamseID->NameID and (2x) Namspace->Namespace o Fix three typos NamseID->NameID and (2x) Namspace->Namespace
draft-ietf-oauth-saml2-bearer-05 draft-ietf-oauth-saml2-bearer-05
skipping to change at page 14, line 4 skipping to change at page 15, line 33
o Updated to reference draft-ietf-oauth-v2-12 and denote as work in o Updated to reference draft-ietf-oauth-v2-12 and denote as work in
progress progress
o Update Parameter Registration Request to use similar terms as o Update Parameter Registration Request to use similar terms as
draft-ietf-oauth-v2-12 and remove Related information part draft-ietf-oauth-v2-12 and remove Related information part
o Add some text giving discretion to AS on rejecting assertions with o Add some text giving discretion to AS on rejecting assertions with
unreasonably long validity window. unreasonably long validity window.
draft-ietf-oauth-saml2-bearer-00 draft-ietf-oauth-saml2-bearer-00
o Added Parameter Registration Request for "assertion" to IANA o Added Parameter Registration Request for "assertion" to IANA
Considerations. Considerations.
o Changed document name to draft-ietf-oauth-saml2-bearer in o Changed document name to draft-ietf-oauth-saml2-bearer in
anticipation of becoming a OAUTH WG item. anticipation of becoming an OAUTH WG item.
o Attempt to move the entire definition of the 'assertion' parameter o Attempt to move the entire definition of the 'assertion' parameter
into this draft (it will no longer be defined in OAuth 2 Protocol into this draft (it will no longer be defined in OAuth 2 Protocol
Framework). Framework).
draft-campbell-oauth-saml-01 draft-campbell-oauth-saml-01
o Updated to reference draft-ietf-oauth-v2-11 and reflect changes o Updated to reference draft-ietf-oauth-v2-11 and reflect changes
from -10 to -11. from -10 to -11.
skipping to change at page 15, line 4 skipping to change at page 16, line 34
o Changed the grant_type (was assertion_type) URI from o Changed the grant_type (was assertion_type) URI from
http://oauth.net/assertion_type/saml/2.0/bearer to http://oauth.net/assertion_type/saml/2.0/bearer to
http://oauth.net/grant_type/assertion/saml/2.0/bearer http://oauth.net/grant_type/assertion/saml/2.0/bearer
o Changed title to include "Grant Type" in it. o Changed title to include "Grant Type" in it.
o Editorial updates based on feedback from the WG and others o Editorial updates based on feedback from the WG and others
(including capitalization of Assertion when referring to SAML). (including capitalization of Assertion when referring to SAML).
draft-campbell-oauth-saml-00 draft-campbell-oauth-saml-00
o Initial I-D
7. References
7.1. Normative References
[I-D.ietf.oauth-assertions]
Mortimore, C., Ed., Campbell, B., Jones, M., and Y.
Goland, "OAuth 2.0 Assertion Profile",
ID draft-ietf-oauth-assertions-00 (work in progress),
July 2011.
[I-D.ietf.oauth-urn-sub-ns]
Campbell, B., Ed. and H. Tschofenig, "An IETF URN Sub-
Namespace for OAuth", ID draft-ietf-oauth-urn-sub-ns-00
(work in progress), Aug 2011.
[I-D.ietf.oauth-v2]
Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, "The
OAuth 2.0 Authorization Protocol",
ID draft-ietf-oauth-v2-16 (work in progress), May 2011.
[OASIS.saml-core-2.0-os]
Cantor, S., Kemp, J., Philpott, R., and E. Maler,
"Assertions and Protocol for the OASIS Security Assertion
Markup Language (SAML) V2.0", OASIS Standard saml-core-
2.0-os, March 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, October 2006.
7.2. Informative References o Initial I-D
[OASIS.saml-deleg-cs]
Cantor, S., Ed., "SAML V2.0 Condition for Delegation
Restriction", Nov 2009.
[OASIS.saml-profiles-2.0-os]
Hughes, J., Cantor, S., Hodges, J., Hirsch, F., Mishra,
P., Philpott, R., and E. Maler, "Profiles for the OASIS
Security Assertion Markup Language (SAML) V2.0", OASIS
Standard OASIS.saml-profiles-2.0-os, March 2005.
[OASIS.saml-sec-consider-2.0-os]
Hirsch, F., Philpott, R., and E. Maler, "Security and
Privacy Considerations for the OASIS Security Markup
Language (SAML) V2.0", OASIS Standard saml-sec-consider-
2.0-os, March 2005.
[W3C.REC-html401-19991224]
Raggett, D., Hors, A., and I. Jacobs, "HTML 4.01
Specification", World Wide Web Consortium
Recommendation REC-html401-19991224, December 1999,
<http://www.w3.org/TR/1999/REC-html401-19991224>.
Authors' Addresses Authors' Addresses
Brian Campbell (editor) Brian Campbell (editor)
Ping Identity Corp. Ping Identity Corp.
Email: brian.d.campbell@gmail.com Email: brian.d.campbell@gmail.com
Chuck Mortimore Chuck Mortimore
Salesforce.com Salesforce.com
 End of changes. 36 change blocks. 
129 lines changed or deleted 152 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/