4Assertions and Protocols for the OASISSecurity Assertion Markup Language(SAML) V2.0

5

OASIS Standard, 15 March 2005

6
7

Document identifier:saml-core-2.0-os

89Location:
http://docs.oasis-open.org/security/saml/v2.0/

10
11
12
13
14

Editors:
Scott Cantor, Internet2
John Kemp, Nokia
Rob Philpott, RSA Security
Eve Maler, Sun Microsystems

15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

SAML V2.0 Contributors:
Conor P. Cahill, AOL
John Hughes, Atos Origin
Hal Lockhart, BEA Systems
Michael Beach, Boeing
Rebekah Metz, Booz Allen Hamilton
Rick Randall, Booz Allen Hamilton
Thomas Wisniewski, Entrust
Irving Reid, Hewlett-Packard
Paula Austel, IBM
Maryann Hondo, IBM
Michael McIntosh, IBM
Tony Nadalin, IBM
Nick Ragouzis, Individual
Scott Cantor, Internet2
RL 'Bob' Morgan, Internet2
Peter C Davis, Neustar
Jeff Hodges, Neustar
Frederick Hirsch, Nokia
John Kemp, Nokia
Paul Madsen, NTT
Steve Anderson, OpenNetwork
Prateek Mishra, Principal Identity
John Linn, RSA Security
Rob Philpott, RSA Security
Jahan Moreh, Sigaba
Anne Anderson, Sun Microsystems

1
2

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

2
3

15 March 2005
Page 1 of 86

Eve Maler, Sun Microsystems
Ron Monzillo, Sun Microsystems
Greg Whitehead, Trustgenix

42
43
44
45
46
47

Abstract:
This specification defines the syntax and semantics for XML-encoded assertions aboutauthentication, attributes, and authorization, and for the protocols that convey this information.

48
49
50

Status:

51
52
53
54
55

This is an OASIS Standard document produced by the Security Services Technical Committee. It
was approved by the OASIS membership on 1 March 2005.
Committee members should submit comments and potential errata to the securityservices@lists.oasis-open.org list. Others should submit them by filling out the web form locatedat http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=security. The
committee will publish on its web page (http://www.oasis-open.org/committees/security) a catalog
of any changes made to this document as a result of comments.

56
57
58
59

For information on whether any patents have been disclosed that may be essential to
implementing this specification, and any offers of patent licensing terms, please refer to theIntellectual Property Rights web page for the Security Services TC (http://www.oasisopen.org/committees/security/ipr.php).

34saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 2 of 86

60

61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109

5
6

Table of Contents
1 Introduction..................................................................................................................................................7
1.1 Notation................................................................................................................................................7
1.2 Schema Organization and Namespaces.............................................................................................8
1.3 Common Data Types...........................................................................................................................8
1.3.1 String Values................................................................................................................................8
1.3.2 URI Values....................................................................................................................................91.3.3 Time Values..................................................................................................................................91.3.4 ID and ID Reference Values.........................................................................................................9
2 SAML Assertions.......................................................................................................................................11
2.1 Schema Header and Namespace Declarations................................................................................ 11
2.2 Name Identifiers.................................................................................................................................122.2.1 Element <BaseID>......................................................................................................................122.2.2 Complex Type NameIDType......................................................................................................132.2.3 Element <NameID>....................................................................................................................142.2.4 Element <EncryptedID>..............................................................................................................142.2.5 Element <Issuer>.......................................................................................................................15
2.3 Assertions..........................................................................................................................................15
2.3.1 Element <AssertionIDRef>.........................................................................................................15
2.3.2 Element <AssertionURIRef>......................................................................................................15
2.3.3 Element <Assertion>..................................................................................................................15
2.3.4 Element <EncryptedAssertion>..................................................................................................17
2.4 Subjects.............................................................................................................................................172.4.1 Element <Subject> ....................................................................................................................18
2.4.1.1 Element <SubjectConfirmation>.........................................................................................18
2.4.1.2 Element <SubjectConfirmationData>..................................................................................192.4.1.3 Complex Type KeyInfoConfirmationDataType....................................................................20
2.4.1.4 Example of a Key-Confirmed <Subject>.............................................................................21
2.5 Conditions..........................................................................................................................................212.5.1 Element <Conditions>................................................................................................................212.5.1.1 General Processing Rules..................................................................................................222.5.1.2 Attributes NotBefore and NotOnOrAfter .............................................................................23
2.5.1.3 Element <Condition>...........................................................................................................23
2.5.1.4 Elements <AudienceRestriction> and <Audience>.............................................................23
2.5.1.5 Element <OneTimeUse>.....................................................................................................24
2.5.1.6 Element <ProxyRestriction>................................................................................................25
2.6 Advice................................................................................................................................................25
2.6.1 Element <Advice>.......................................................................................................................26
2.7 Statements.........................................................................................................................................26
2.7.1 Element <Statement>.................................................................................................................26
2.7.2 Element <AuthnStatement>.......................................................................................................26
2.7.2.1 Element <SubjectLocality>..................................................................................................28
2.7.2.2 Element <AuthnContext>....................................................................................................28
2.7.3 Element <AttributeStatement>...................................................................................................29
2.7.3.1 Element <Attribute>.............................................................................................................29
2.7.3.1.1 Element <AttributeValue>............................................................................................30
2.7.3.2 Element <EncryptedAttribute>............................................................................................31
2.7.4 Element <AuthzDecisionStatement>..........................................................................................31
2.7.4.1 Simple Type DecisionType..................................................................................................33
2.7.4.2 Element <Action>................................................................................................................33

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 3 of 86

110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162

7
8

2.7.4.3 Element <Evidence>...........................................................................................................34
3 SAML Protocols.........................................................................................................................................35
3.1 Schema Header and Namespace Declarations................................................................................ 35
3.2 Requests and Responses..................................................................................................................36
3.2.1 Complex Type RequestAbstractType.........................................................................................36
3.2.2 Complex Type StatusResponseType.........................................................................................38
3.2.2.1 Element <Status>................................................................................................................39
3.2.2.2 Element <StatusCode>.......................................................................................................39
3.2.2.3 Element <StatusMessage>.................................................................................................423.2.2.4 Element <StatusDetail>.......................................................................................................42
3.3 Assertion Query and Request Protocol..............................................................................................423.3.1 Element <AssertionIDRequest>.................................................................................................423.3.2 Queries.......................................................................................................................................423.3.2.1 Element <SubjectQuery>....................................................................................................423.3.2.2 Element <AuthnQuery>.......................................................................................................43
3.3.2.2.1 Element <RequestedAuthnContext>...........................................................................44
3.3.2.3 Element <AttributeQuery>...................................................................................................45
3.3.2.4 Element <AuthzDecisionQuery>.........................................................................................46
3.3.3 Element <Response>.................................................................................................................46
3.3.4 Processing Rules........................................................................................................................47
3.4 Authentication Request Protocol........................................................................................................47
3.4.1 Element <AuthnRequest>..........................................................................................................48
3.4.1.1 Element <NameIDPolicy>...................................................................................................50
3.4.1.2 Element <Scoping>.............................................................................................................51
3.4.1.3 Element <IDPList>..............................................................................................................52
3.4.1.3.1 Element <IDPEntry>....................................................................................................52
3.4.1.4 Processing Rules................................................................................................................53
3.4.1.5 Proxying...............................................................................................................................54
3.4.1.5.1 Proxying Processing Rules..........................................................................................54
3.5 Artifact Resolution Protocol................................................................................................................55
3.5.1 Element <ArtifactResolve>.........................................................................................................56
3.5.2 Element <ArtifactResponse>......................................................................................................56
3.5.3 Processing Rules........................................................................................................................56
3.6 Name Identifier Management Protocol..............................................................................................57
3.6.1 Element <ManageNameIDRequest>..........................................................................................57
3.6.2 Element <ManageNameIDResponse>.......................................................................................58
3.6.3 Processing Rules........................................................................................................................58
3.7 Single Logout Protocol.......................................................................................................................59
3.7.1 Element <LogoutRequest>.........................................................................................................60
3.7.2 Element <LogoutResponse>......................................................................................................60
3.7.3 Processing Rules........................................................................................................................61
3.7.3.1 Session Participant Rules...................................................................................................61
3.7.3.2 Session Authority Rules......................................................................................................62
3.8 Name Identifier Mapping Protocol......................................................................................................63
3.8.1 Element <NameIDMappingRequest>.........................................................................................63
3.8.2 Element <NameIDMappingResponse>......................................................................................64
3.8.3 Processing Rules........................................................................................................................64
4 SAML Versioning.......................................................................................................................................65
4.1 SAML Specification Set Version........................................................................................................65
4.1.1 Schema Version.........................................................................................................................65
4.1.2 SAML Assertion Version.............................................................................................................65
4.1.3 SAML Protocol Version...............................................................................................................66
4.1.3.1 Request Version..................................................................................................................66

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 4 of 86

163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213

9
10

4.1.3.2 Response Version...............................................................................................................66
4.1.3.3 Permissible Version Combinations.....................................................................................67
4.2 SAML Namespace Version................................................................................................................67
4.2.1 Schema Evolution.......................................................................................................................67
5 SAML and XML Signature Syntax and Processing...................................................................................68
5.1 Signing Assertions.............................................................................................................................68
5.2 Request/Response Signing...............................................................................................................68
5.3 Signature Inheritance.........................................................................................................................68
5.4 XML Signature Profile........................................................................................................................69
5.4.1 Signing Formats and Algorithms................................................................................................69
5.4.2 References.................................................................................................................................69
5.4.3 Canonicalization Method............................................................................................................69
5.4.4 Transforms.................................................................................................................................69
5.4.5 KeyInfo........................................................................................................................................70
5.4.6 Example......................................................................................................................................70
6 SAML and XML Encryption Syntax and Processing................................................................................. 73
6.1 General Considerations.....................................................................................................................73
6.2 Combining Signatures and Encryption...............................................................................................73
7 SAML Extensibility.....................................................................................................................................74
7.1 Schema Extension.............................................................................................................................74
7.1.1 Assertion Schema Extension......................................................................................................74
7.1.2 Protocol Schema Extension.......................................................................................................74
7.2 Schema Wildcard Extension Points...................................................................................................75
7.2.1 Assertion Extension Points.........................................................................................................75
7.2.2 Protocol Extension Points...........................................................................................................75
7.3 Identifier Extension.............................................................................................................................75
8 SAML-Defined Identifiers..........................................................................................................................76
8.1 Action Namespace Identifiers............................................................................................................76
8.1.1 Read/Write/Execute/Delete/Control...........................................................................................76
8.1.2 Read/Write/Execute/Delete/Control with Negation.....................................................................76
8.1.3 Get/Head/Put/Post......................................................................................................................77
8.1.4 UNIX File Permissions................................................................................................................77
8.2 Attribute Name Format Identifiers......................................................................................................77
8.2.1 Unspecified.................................................................................................................................77
8.2.2 URI Reference............................................................................................................................78
8.2.3 Basic...........................................................................................................................................78
8.3 Name Identifier Format Identifiers.....................................................................................................78
8.3.1 Unspecified.................................................................................................................................78
8.3.2 Email Address.............................................................................................................................78
8.3.3 X.509 Subject Name...................................................................................................................78
8.3.4 Windows Domain Qualified Name..............................................................................................78
8.3.5 Kerberos Principal Name............................................................................................................79
8.3.6 Entity Identifier............................................................................................................................79
8.3.7 Persistent Identifier.....................................................................................................................79
8.3.8 Transient Identifier......................................................................................................................80
8.4 Consent Identifiers.............................................................................................................................80
8.4.1 Unspecified.................................................................................................................................80
8.4.2 Obtained.....................................................................................................................................80
8.4.3 Prior............................................................................................................................................80
8.4.4 Implicit.........................................................................................................................................81
8.4.5 Explicit........................................................................................................................................81

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 5 of 86

214
215
216
217
218
219
220

8.4.6 Unavailable.................................................................................................................................81
8.4.7 Inapplicable.................................................................................................................................81
9 References................................................................................................................................................82
9.1 Normative References.......................................................................................................................82
9.2 Non-Normative References...............................................................................................................82
Appendix A. Acknowledgments....................................................................................................................84
Appendix B. Notices.....................................................................................................................................86

221

11
12

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 6 of 86

222

1 Introduction

223
224
225
226
227

The Security Assertion Markup Language (SAML) defines the syntax and processing semantics ofassertions made about a subject by a system entity. In the course of making, or relying upon suchassertions, SAML system entities may use other protocols to communicate either regarding an assertion
itself, or the subject of an assertion. This specification defines both the structure of SAML assertions, andan associated set of protocols, in addition to the processing rules involved in managing a SAML system.

228
229
230
231
232
233

SAML assertions and protocol messages are encoded in XML [XML] and use XML namespaces[XMLNS]. They are typically embedded in other structures for transport, such as HTTP POST requests or
XML-encoded SOAP messages. The SAML bindings specification [SAMLBind] provides frameworks forthe embedding and transport of SAML protocol messages. The SAML profiles specification [SAMLProf]
provides a baseline set of profiles for the use of SAML assertions and protocols to accomplish specificuse cases or achieve interoperability when using SAML features.

234
235
236
237

For additional explanation of SAML terms and concepts, refer to the SAML technical overview[SAMLTechOvw] and the SAML glossary [SAMLGloss] . Files containing just the SAML assertion schema[SAML-XSD] and protocol schema [SAMLP-XSD] are also available. The SAML conformance document[SAMLConform] lists all of the specifications that comprise SAML V2.0.

238

The following sections describe how to understand the rest of this specification.

239

1.1 Notation

240
241
242

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as
described in IETF RFC 2119 [RFC 2119].

243

Listings of SAML schemas appear like this.

244
245

Example code listings appear like this.

Note: Notes like this are sometimes used to highlight non-normative commentary.

246
247
248
249
250
251

This specification uses schema documents conforming to W3C XML Schema [Schema1] and normative
text to describe the syntax and semantics of XML-encoded SAML assertions and protocol messages. In
cases of disagreement between the SAML schema documents and schema listings in this specification,
the schema documents take precedence. Note that in some cases the normative text of this specification
imposes constraints beyond those indicated by the schema documents.

252
253
254

Conventional XML namespace prefixes are used throughout the listings in this specification to stand fortheir respective namespaces (see Section 1.2) as follows, whether or not a namespace declaration ispresent in the example:
Prefix13
14

XML Namespace

Commentssaml:

urn:oasis:names:tc:SAML:2.0:assertion This is the SAML V2.0 assertion namespace, defined in aschema [SAML-XSD]. The prefix is generally elided inmentions of SAML assertion-related elements in text.

samlp:

urn:oasis:names:tc:SAML:2.0:protocol

This is the SAML V2.0 protocol namespace, defined in aschema [SAMLP-XSD]. The prefix is generally elided inmentions of XML protocol-related elements in text.

ds:

http://www.w3.org/2000/09/xmldsig#

This namespace is defined in the XML Signature Syntax andProcessing specification [XMLSig] and its governing schema[XMLSig-XSD].

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 7 of 86

Prefix

XML Namespace

Comments

xenc:

http://www.w3.org/2001/04/xmlenc#

This namespace is defined in the XML Encryption Syntax
and Processing specification [XMLEnc] and its governing
schema [XMLEnc-XSD].

xs:

http://www.w3.org/2001/XMLSchemaThis namespace is defined in the W3C XML Schema
specification [Schema1]. In schema listings, this is thedefault namespace and no prefix is shown. For clarity, theprefix is generally shown in specification text when XML
Schema-related constructs are mentioned.

xsi:

http://www.w3.org/2001/XMLSchemainstanceThis namespace is defined in the W3C XML Schema
specification [Schema1] for schema-related markup thatappears in XML instances.

255
256

This specification uses the following typographical conventions in text: <SAMLElement>,<ns:ForeignElement>, XMLAttribute, Datatype, OtherKeyword.

257

1.2 Schema Organization and Namespaces

258
259

The SAML assertion structures are defined in a schema [SAML-XSD] associated with the following XML
namespace:

260
261
262
263

urn:oasis:names:tc:SAML:2.0:assertion

The SAML request-response protocol structures are defined in a schema [SAMLP-XSD] associated withthe following XML namespace:
urn:oasis:names:tc:SAML:2.0:protocol

264
265

The assertion schema is imported into the protocol schema. See Section 4.2 for information on SAML
namespace versioning.

266
267

Also imported into both schemas is the schema for XML Signature [XMLSig], which is associated with thefollowing XML namespace:

268
269
270
271

http://www.w3.org/2000/09/xmldsig#

Finally, the schema for XML Encryption [XMLEnc] is imported into the assertion schema and is associatedwith the following XML namespace:http://www.w3.org/2001/04/xmlenc#

272

1.3 Common Data Types

273
274

The following sections define how to use and interpret common data types that appear throughout the
SAML schemas.

275

1.3.1 String Values

276
277
278
279

All SAML string values have the type xs:string, which is built in to the W3C XML Schema Datatypes
specification [Schema2]. Unless otherwise noted in this specification or particular profiles, all strings in
SAML messages MUST consist of at least one non-whitespace character (whitespace is defined in the
XML Recommendation [XML] Section 2.3).

280
281
282
283

Unless otherwise noted in this specification or particular profiles, all elements in SAML documents thathave the XML Schema xs:string type, or a type derived from that, MUST be compared using an exact
binary comparison. In particular, SAML implementations and deployments MUST NOT depend on caseinsensitive string comparisons, normalization or trimming of whitespace, or conversion of locale-specific1516saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 8 of 86

284
285

formats such as numbers or currency. This requirement is intended to conform to the W3C working-draft
Requirements for String Identity, Matching, and String Indexing [W3C-CHAR].

286
287
288
289
290

If an implementation is comparing values that are represented using different character encodings, theimplementation MUST use a comparison method that returns the same result as converting both values tothe Unicode character encoding, Normalization Form C [UNICODE-C], and then performing an exact
binary comparison. This requirement is intended to conform to the W3C Character Model for the World
Wide Web [W3C-CharMod], and in particular the rules for Unicode-normalized Text.

291
292
293
294
295
296

Applications that compare data received in SAML documents to data from external sources MUST take
into account the normalization rules specified for XML. Text contained within elements is normalized sothat line endings are represented using linefeed characters (ASCII code 10Decimal), as described in the XML
Recommendation [XML] Section 2.11. XML attribute values defined as strings (or types derived fromstrings) are normalized as described in [XML] Section 3.3.3. All whitespace characters are replaced withblanks (ASCII code 32Decimal).

297
298
299

The SAML specification does not define collation or sorting order for XML attribute values or element
content. SAML implementations MUST NOT depend on specific sorting orders for values, because thesecan differ depending on the locale settings of the hosts involved.

300

1.3.2 URI Values

301
302

All SAML URI reference values have the type xs:anyURI, which is built in to the W3C XML Schema
Datatypes specification [Schema2].

303
304
305

Unless otherwise indicated in this specification, all URI reference values used within SAML-definedelements or attributes MUST consist of at least one non-whitespace character, and are REQUIRED to beabsolute [RFC 2396].

306
307
308
309

Note that the SAML specification makes extensive use of URI references as identifiers, such as status
codes, format types, attribute and system entity names, etc. In such cases, it is essential that the values
be both unique and consistent, such that the same URI is never used at different times to represent
different underlying information.

310

1.3.3 Time Values

311
312

All SAML time values have the type xs:dateTime, which is built in to the W3C XML Schema Datatypes
specification [Schema2], and MUST be expressed in UTC form, with no time zone component.

313
314

SAML system entities SHOULD NOT rely on time resolution finer than milliseconds. Implementations
MUST NOT generate time instants that specify leap seconds.

315

1.3.4 ID and ID Reference Values

316
317
318

The xs:ID simple type is used to declare SAML identifiers for assertions, requests, and responses. Values
declared to be of type xs:ID in this specification MUST satisfy the following properties in addition to those
imposed by the definition of the xs:ID type itself:

319
320

• Any party that assigns an identifier MUST ensure that there is negligible probability that that party or
any other party will accidentally assign the same identifier to a different data object.

321
322

• Where a data object declares that it has a particular identifier, there MUST be exactly one suchdeclaration.

323
324
325
326

The mechanism by which a SAML system entity ensures that the identifier is unique is left to theimplementation. In the case that a random or pseudorandom technique is employed, the probability of two
randomly chosen identifiers being identical MUST be less than or equal to 2-128 and SHOULD be less thanor equal to 2-160. This requirement MAY be met by encoding a randomly chosen value between 128 and17
18

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 9 of 86

327
328
329

160 bits in length. The encoding must conform to the rules defining the xs:ID datatype. A pseudorandom
generator MUST be seeded with unique material in order to ensure the desired uniqueness properties
between different systems.

330
331
332
333
334

The xs:NCName simple type is used in SAML to reference identifiers of type xs:ID since xs:IDREF
cannot be used for this purpose. In SAML, the element referred to by a SAML identifier reference might
actually be defined in a document separate from that in which the identifier reference is used. Using
xs:IDREF would violate the requirement that its value match the value of an ID attribute on some elementin the same XML document.

335
336
337
338
339

Note: It is anticipated that the World Wide Web Consortium will standardize a global
attribute for holding ID-typed values, called xml:id [XML-ID]. The Security Services
Technical Committee plans to move away from SAML-specific ID attributes to this style ofassigning unique identifiers as soon as practicable after the xml:id attribute isstandardized.

19
20

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 10 of 86

340

2 SAML Assertions

341
342
343
344
345

An assertion is a package of information that supplies zero or more statements made by a SAML
authority; SAML authorities are sometimes referred to as asserting parties in discussions of assertion
generation and exchange, and system entities that use received assertions are known as relying parties.
(Note that these terms are different from requester and responder, which are reserved for discussions of
SAML protocol message exchange.)

346
347
348
349
350
351

SAML assertions are usually made about a subject, represented by the <Subject> element. However,the <Subject> element is optional, and other specifications and profiles may utilize the SAML assertion
structure to make similar statements without specifying a subject, or possibly specifying the subject in analternate way. Typically there are a number of service providers that can make use of assertions about asubject in order to control access and provide customized service, and accordingly they become therelying parties of an asserting party called an identity provider.

352
353
354

This SAML specification defines three different kinds of assertion statements that can be created by a
SAML authority. All SAML-defined statements are associated with a subject. The three kinds of statement
defined in this specification are:355

• Authentication: The assertion subject was authenticated by a particular means at a particular time.

356• Attribute: The assertion subject is associated with the supplied attributes.

357
358

• Authorization Decision: A request to allow the assertion subject to access the specified resource
has been granted or denied.

359
360
361

The outer structure of an assertion is generic, providing information that is common to all of thestatements within it. Within an assertion, a series of inner elements describe the authentication, attribute,
authorization decision, or user-defined statements containing the specifics.

362
363
364

As described in Section 7, extensions are permitted by the SAML assertion schema, allowing user-defined
extensions to assertions and statements, as well as allowing the definition of new kinds of assertions andstatements.

365
366

The SAML technical overview [SAMLTechOvw] and glossary [SAMLGloss] provide more detailed
explanation of SAML terms and concepts.

367

2.1 Schema Header and Namespace Declarations

368
369

The following schema fragment defines the XML namespaces and other header information for theassertion schema:

370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387

21
22

<schema targetNamespace="urn:oasis:names:tc:SAML:2.0:assertion"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
elementFormDefault="unqualified"attributeFormDefault="unqualified"
blockDefault="substitution"version="2.0"><import namespace="http://www.w3.org/2000/09/xmldsig#"
schemaLocation="http://www.w3.org/TR/2002/REC-xmldsig-core20020212/xmldsig-core-schema.xsd"/><import namespace="http://www.w3.org/2001/04/xmlenc#"
schemaLocation="http://www.w3.org/TR/2002/REC-xmlenc-core20021210/xenc-schema.xsd"/><annotation><documentation>
Document identifier: saml-schema-assertion-2.0

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 11 of 86

388
389
390
391
392
393
394
395
396
397
398
399

Location: http://docs.oasis-open.org/security/saml/v2.0/
Revision history:
V1.0 (November, 2002):
Initial Standard Schema.
V1.1 (September, 2003):
Updates within the same V1.0 namespace.
V2.0 (March, 2005):
New assertion schema for SAML V2.0 namespace.
</documentation></annotation>…
</schema>400

2.2 Name Identifiers

401
402

The following sections define the SAML constructs that contain descriptive identifiers for subjects and theissuers of assertions and protocol messages.

403
404
405
406
407
408
409

There are a number of circumstances in SAML in which it is useful for two system entities to communicate
regarding a third party; for example, the SAML authentication request protocol enables third-party
authentication of a subject. Thus, it is useful to establish a means by which parties may be associatedwith identifiers that are meaningful to each of the parties. In some cases, it will be necessary to limit thescope within which an identifier is used to a small set of system entities (to preserve the privacy of a
subject, for example). Similar identifiers may also be used to refer to the issuer of a SAML protocol
message or assertion.

410
411
412
413
414
415

It is possible that two or more system entities may use the same name identifier value when referring todifferent identities. Thus, each entity may have a different understanding of that same name. SAML
provides name qualifiers to disambiguate a name identifier by effectively placing it in a federated
namespace related to the name qualifiers. SAML V2.0 allows an identifier to be qualified in terms of bothan asserting party and a particular relying party or affiliation, allowing identifiers to exhibit pair-wisesemantics, when required.

416
417

Name identifiers may also be encrypted to further improve their privacy-preserving characteristics,
particularly in cases where the identifier may be transmitted via an intermediary.

418
419

Note: To avoid use of relatively advanced XML schema constructs (among otherreasons), the various types of identifier elements do not share a common type hierarchy.

420

2.2.1 Element <BaseID>

421
422
423

The <BaseID> element is an extension point that allows applications to add new kinds of identifiers. Its
BaseIDAbstractType complex type is abstract and is thus usable only as the base of a derived type. It
includes the following attributes for use by extended identifier representations:

424

NameQualifier [Optional]

425
426
427
428
429
430

The security or administrative domain that qualifies the identifier. This attribute provides a means
to federate identifiers from disparate user stores without collision.
SPNameQualifier [Optional]
Further qualifies an identifier with the name of a service provider or affiliation of providers. This
attribute provides an additional means to federate identifiers on the basis of the relying party or
parties.

431
432

The NameQualifier and SPNameQualifier attributes SHOULD be omitted unless the identifier's typedefinition explicitly defines their use and semantics.

23
24

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 12 of 86

433
434
435
436
437
438
439
440
441
442

The following schema fragment defines the <BaseID> element and its BaseIDAbstractType complex
type:<attributeGroup name="IDNameQualifiers"><attribute name="NameQualifier" type="string" use="optional"/><attribute name="SPNameQualifier" type="string" use="optional"/></attributeGroup><element name="BaseID" type="saml:BaseIDAbstractType"/><complexType name="BaseIDAbstractType" abstract="true"><attributeGroup ref="saml:IDNameQualifiers"/></complexType>443

2.2.2 Complex Type NameIDType

444
445
446
447

The NameIDType complex type is used when an element serves to represent an entity by a string-valued
name. It is a more restricted form of identifier than the <BaseID> element and is the type underlying boththe <NameID> and <Issuer> elements. In addition to the string content containing the actual identifier, it
provides the following optional attributes:

448
449
450

NameQualifier [Optional]
The security or administrative domain that qualifies the name. This attribute provides a means tofederate names from disparate user stores without collision.

451

SPNameQualifier [Optional]

452
453
454
455

Further qualifies a name with the name of a service provider or affiliation of providers. This
attribute provides an additional means to federate names on the basis of the relying party or
parties.
Format [Optional]

457
458
459
460
461

A URI reference representing the classification of string-based identifier information. See Section
8.3 for the SAML-defined URI references that MAY be used as the value of the Format attributeand their associated descriptions and processing rules. Unless otherwise specified by an element
based on this type, if no Format value is provided, then the value
urn:oasis:names:tc:SAML:1.0:nameid-format:unspecified (see Section 8.3.1) is ineffect.

462
463
464
465
466

When a Format value other than one specified in Section 8.3 is used, the content of an elementof this type is to be interpreted according to the definition of that format as provided outside of thisspecification. If not otherwise indicated by the definition of the format, issues of anonymity,
pseudonymity, and the persistence of the identifier with respect to the asserting and relying parties
are implementation-specific.

456

467

SPProvidedID [Optional]

468
469
470
471
472

A name identifier established by a service provider or affiliation of providers for the entity, if
different from the primary name identifier given in the content of the element. This attributeprovides a means of integrating the use of SAML with existing identifiers already in use by aservice provider. For example, an existing identifier can be "attached" to the entity using the Name
Identifier Management protocol defined in Section 3.6.

473
474
475

Additional rules for the content of (or the omission of) these attributes can be defined by elements thatmake use of this type, and by specific Format definitions. The NameQualifier and SPNameQualifier
attributes SHOULD be omitted unless the element or format explicitly defines their use and semantics.

476

The following schema fragment defines the NameIDType complex type:

477
478

<complexType name="NameIDType"><simpleContent>

25
26

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 13 of 86

479
480
481
482
483
484
485

<extension base="string"><attributeGroup ref="saml:IDNameQualifiers"/><attribute name="Format" type="anyURI" use="optional"/><attribute name="SPProvidedID" type="string" use="optional"/></extension></simpleContent></complexType>486

2.2.3 Element <NameID>

487
488
489

The <NameID> element is of type NameIDType (see Section 2.2.2), and is used in various SAML
assertion constructs such as the <Subject> and <SubjectConfirmation> elements, and in various
protocol messages (see Section 3).

490

The following schema fragment defines the <NameID> element:491<element name="NameID" type="saml:NameIDType"/>492

2.2.4 Element <EncryptedID>

493
494
495

The <EncryptedID> element is of type EncryptedElementType, and carries the content of an
unencrypted identifier element in encrypted fashion, as defined by the XML Encryption Syntax andProcessing specification [XMLEnc]. The <EncryptedID> element contains the following elements:

496<xenc:EncryptedData> [Required]

497
498
499
500
501
502

The encrypted content and associated encryption details, as defined by the XML Encryption
Syntax and Processing specification [XMLEnc]. The Type attribute SHOULD be present and, if
present, MUST contain a value of http://www.w3.org/2001/04/xmlenc#Element. The
encrypted content MUST contain an element that has a type of NameIDType or AssertionType,or a type that is derived from BaseIDAbstractType, NameIDType, or AssertionType.
<xenc:EncryptedKey> [Zero or More]

503
504
505
506

Wrapped decryption keys, as defined by [XMLEnc]. Each wrapped key SHOULD include a
Recipient attribute that specifies the entity for whom the key has been encrypted. The value of
the Recipient attribute SHOULD be the URI identifier of a SAML system entity, as defined by
Section 8.3.6.

507
508
509

Encrypted identifiers are intended as a privacy protection mechanism when the plain-text value passes
through an intermediary. As such, the ciphertext MUST be unique to any given encryption operation. For
more on such issues, see [XMLEnc] Section 6.3.

510
511
512

Note that an entire assertion can be encrypted into this element and used as an identifier. In such a case,the <Subject> element of the encrypted assertion supplies the "identifier" of the subject of the enclosing
assertion. Note also that if the identifying assertion is invalid, then so is the enclosing assertion.

513
514

The following schema fragment defines the <EncryptedID> element and its EncryptedElementTypecomplex type:

515
516
517
518
519
520
521

<complexType name="EncryptedElementType"><sequence><element ref="xenc:EncryptedData"/><element ref="xenc:EncryptedKey" minOccurs="0" maxOccurs="unbounded"/></sequence></complexType><element name="EncryptedID" type="saml:EncryptedElementType"/>27
28

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 14 of 86

522

2.2.5 Element <Issuer>

523
524
525

The <Issuer> element, with complex type NameIDType, provides information about the issuer of a
SAML assertion or protocol message. The element requires the use of a string to carry the issuer's name,but permits various pieces of descriptive data (see Section 2.2.2).

526
527

Overriding the usual rule for this element's type, if no Format value is provided with this element, then thevalue urn:oasis:names:tc:SAML:2.0:nameid-format:entity is in effect (see Section 8.3.6).

528

The following schema fragment defines the <Issuer> element:529<element name="Issuer" type="saml:NameIDType"/>530

2.3 Assertions

531
532

The following sections define the SAML constructs that either contain assertion information or provide ameans to refer to an existing assertion.

533

2.3.1 Element <AssertionIDRef>

534
535
536
537

The <AssertionIDRef> element makes a reference to a SAML assertion by its unique identifier. The
specific authority who issued the assertion or from whom the assertion can be obtained is not specified aspart of the reference. See Section 3.3.1 for a protocol element that uses such a reference to ask for thecorresponding assertion.

538

The following schema fragment defines the <AssertionIDRef> element:539<element name="AssertionIDRef" type="NCName"/>540

2.3.2 Element <AssertionURIRef>

541
542
543
544

The <AssertionURIRef> element makes a reference to a SAML assertion by URI reference. The URI
reference MAY be used to retrieve the corresponding assertion in a manner specific to the URI reference.
See Section 3.7 of the Bindings specification [SAMLBind] for information on how this element is used in a
protocol binding to accomplish this.

545

The following schema fragment defines the <AssertionURIRef> element:546<element name="AssertionURIRef" type="anyURI"/>

547

2.3.3 Element <Assertion>

548
549

The <Assertion> element is of the AssertionType complex type. This type specifies the basic
information that is common to all assertions, including the following elements and attributes:

550

Version [Required]

551
552
553
554
555
556
557

29
30

The version of this assertion. The identifier for the version of SAML defined in this specification is"2.0". SAML versioning is discussed in Section 4.
ID [Required]
The identifier for this assertion. It is of type xs:ID, and MUST follow the requirements specified in
Section 1.3.4 for identifier uniqueness.
IssueInstant [Required]
The time instant of issue in UTC, as described in Section 1.3.3.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 15 of 86

558<Issuer> [Required]

559
560

The SAML authority that is making the claim(s) in the assertion. The issuer SHOULD be unambiguous
to the intended relying parties.

561
562
563

This specification defines no particular relationship between the entity represented by this element
and the signer of the assertion (if any). Any such requirements imposed by a relying party that
consumes the assertion or by specific profiles are application-specific.

564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579

<ds:Signature> [Optional]
An XML Signature that protects the integrity of and authenticates the issuer of the assertion, as
described below and in Section 5.
<Subject> [Optional]
The subject of the statement(s) in the assertion.
<Conditions> [Optional]
Conditions that MUST be evaluated when assessing the validity of and/or when using the assertion.
See Section 2.5 for additional information on how to evaluate conditions.
<Advice> [Optional]
Additional information related to the assertion that assists processing in certain situations but which
MAY be ignored by applications that do not understand the advice or do not wish to make use of it.
Zero or more of the following statement elements:<Statement>
A statement of a type defined in an extension schema. An xsi:type attribute MUST be used toindicate the actual statement type.
<AuthnStatement>

580

An authentication statement.

581<AuthzDecisionStatement>582

An authorization decision statement.

583<AttributeStatement>

584

An attribute statement.

585
586
587

An assertion with no statements MUST contain a <Subject> element. Such an assertion identifies aprincipal in a manner which can be referenced or confirmed using SAML methods, but asserts no further
information associated with that principal.

588
589
590
591

Otherwise <Subject>, if present, identifies the subject of all of the statements in the assertion. If<Subject> is omitted, then the statements in the assertion apply to a subject or subjects identified in an
application- or profile-specific manner. SAML itself defines no such statements, and an assertion without asubject has no defined meaning in this specification.

592
593
594
595
596

Depending on the requirements of particular protocols or profiles, the issuer of a SAML assertion may
often need to be authenticated, and integrity protection may often be required. Authentication andmessage integrity MAY be provided by mechanisms provided by a protocol binding in use during thedelivery of an assertion (see [SAMLBind]). The SAML assertion MAY be signed, which provides bothauthentication of the issuer and integrity protection.

597
598
599
600
601

If such a signature is used, then the <ds:Signature> element MUST be present, and a relying party
MUST verify that the signature is valid (that is, that the assertion has not been tampered with) inaccordance with [XMLSig]. If it is invalid, then the relying party MUST NOT rely on the contents of theassertion. If it is valid, then the relying party SHOULD evaluate the signature to determine the identity andappropriateness of the issuer and may continue to process the assertion in accordance with this31
32

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 16 of 86

602
603

specification and as it deems appropriate (for example, evaluating conditions, advice, following profilespecific rules, and so on).

604
605
606

Note that whether signed or unsigned, the inclusion of multiple statements within a single assertion issemantically equivalent to a set of assertions containing those statements individually (provided thesubject, conditions, etc. are also the same).

607

The following schema fragment defines the <Assertion> element and its AssertionType complex type:

608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626

<element name="Assertion" type="saml:AssertionType"/><complexType name="AssertionType"><sequence><element ref="saml:Issuer"/><element ref="ds:Signature" minOccurs="0"/><element ref="saml:Subject" minOccurs="0"/><element ref="saml:Conditions" minOccurs="0"/><element ref="saml:Advice" minOccurs="0"/><choice minOccurs="0" maxOccurs="unbounded"><element ref="saml:Statement"/><element ref="saml:AuthnStatement"/><element ref="saml:AuthzDecisionStatement"/><element ref="saml:AttributeStatement"/></choice></sequence><attribute name="Version" type="string" use="required"/><attribute name="ID" type="ID" use="required"/><attribute name="IssueInstant" type="dateTime" use="required"/></complexType>

627

2.3.4 Element <EncryptedAssertion>

628
629
630

The <EncryptedAssertion> element represents an assertion in encrypted fashion, as defined by the
XML Encryption Syntax and Processing specification [XMLEnc]. The <EncryptedAssertion> element
contains the following elements:

631<xenc:EncryptedData> [Required]

632
633
634
635
636
637
638
639
640

The encrypted content and associated encryption details, as defined by the XML Encryption
Syntax and Processing specification [XMLEnc]. The Type attribute SHOULD be present and, if
present, MUST contain a value of http://www.w3.org/2001/04/xmlenc#Element. The
encrypted content MUST contain an element that has a type of or derived from AssertionType.
<xenc:EncryptedKey> [Zero or More]
Wrapped decryption keys, as defined by [XMLEnc]. Each wrapped key SHOULD include a
Recipient attribute that specifies the entity for whom the key has been encrypted. The value of
the Recipient attribute SHOULD be the URI identifier of a SAML system entity as defined by
Section 8.3.6.

641
642

Encrypted assertions are intended as a confidentiality protection mechanism when the plain-text value
passes through an intermediary.

643

The following schema fragment defines the <EncryptedAssertion> element:644<element name="EncryptedAssertion" type="saml:EncryptedElementType"/>645

2.4 Subjects

646This section defines the SAML constructs used to describe the subject of an assertion.

33
34

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 17 of 86

647

2.4.1 Element <Subject>

648
649
650

The optional <Subject> element specifies the principal that is the subject of all of the (zero or more)statements in the assertion. It contains an identifier, a series of one or more subject confirmations, or
both:

651

<BaseID>, <NameID>, or <EncryptedID> [Optional]

652
653

Identifies the subject.
<SubjectConfirmation> [Zero or More]

654
655
656

Information that allows the subject to be confirmed. If more than one subject confirmation is provided,
then satisfying any one of them is sufficient to confirm the subject for the purpose of applying theassertion.

657
658
659
660
661

A <Subject> element can contain both an identifier and zero or more subject confirmations which a
relying party can verify when processing an assertion. If any one of the included subject confirmations areverified, the relying party MAY treat the entity presenting the assertion as one that the asserting party has
associated with the principal identified in the name identifier and associated with the statements in theassertion. This attesting entity and the actual subject may or may not be the same entity.

662
663

If there are no subject confirmations included, then any relationship between the presenter of the assertionand the actual subject is unspecified.

664

A <Subject> element SHOULD NOT identify more than one principal.

665

The following schema fragment defines the <Subject> element and its SubjectType complex type:

666
667
668
669
670
671
672
673
674
675
676
677
678
679
680

<element name="Subject" type="saml:SubjectType"/><complexType name="SubjectType"><choice><sequence><choice><element ref="saml:BaseID"/><element ref="saml:NameID"/><element ref="saml:EncryptedID"/></choice><element ref="saml:SubjectConfirmation" minOccurs="0"
maxOccurs="unbounded"/></sequence><element ref="saml:SubjectConfirmation" maxOccurs="unbounded"/></choice></complexType>

681

2.4.1.1 Element <SubjectConfirmation>

682
683
684

The <SubjectConfirmation> element provides the means for a relying party to verify thecorrespondence of the subject of the assertion with the party with whom the relying party iscommunicating. It contains the following attributes and elements:

685

Method [Required]

686
687
688
689
690
691

35
36

A URI reference that identifies a protocol or mechanism to be used to confirm the subject. URI
references identifying SAML-defined confirmation methods are currently defined in the SAML profiles
specification [SAMLProf]. Additional methods MAY be added by defining new URIs and profiles or by
private agreement.
<BaseID>, <NameID>, or <EncryptedID> [Optional]
Identifies the entity expected to satisfy the enclosing subject confirmation requirements.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 18 of 86

692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711

<SubjectConfirmationData> [Optional]
Additional confirmation information to be used by a specific confirmation method. For example, typicalcontent of this element might be a <ds:KeyInfo> element as defined in the XML Signature Syntax
and Processing specification [XMLSig], which identifies a cryptographic key (See also Section
2.4.1.3). Particular confirmation methods MAY define a schema type to describe the elements,
attributes, or content that may appear in the <SubjectConfirmationData> element.
The following schema fragment defines the <SubjectConfirmation> element and its
SubjectConfirmationType complex type:<element name="SubjectConfirmation" type="saml:SubjectConfirmationType"/><complexType name="SubjectConfirmationType"><sequence><choice minOccurs="0"><element ref="saml:BaseID"/><element ref="saml:NameID"/><element ref="saml:EncryptedID"/></choice><element ref="saml:SubjectConfirmationData" minOccurs="0"/></sequence><attribute name="Method" type="anyURI" use="required"/></complexType>712

2.4.1.2 Element <SubjectConfirmationData>

713
714
715
716
717
718

The <SubjectConfirmationData> element has the SubjectConfirmationDataType complex type. It
specifies additional data that allows the subject to be confirmed or constrains the circumstances underwhich the act of subject confirmation can take place. Subject confirmation takes place when a relying
party seeks to verify the relationship between an entity presenting the assertion (that is, the attesting
entity) and the subject of the assertion's claims. It contains the following optional attributes that can apply
to any method:

719

NotBefore [Optional]

720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739

37
38

A time instant before which the subject cannot be confirmed. The time value is encoded in UTC, as
described in Section 1.3.3.
NotOnOrAfter [Optional]
A time instant at which the subject can no longer be confirmed. The time value is encoded in UTC, as
described in Section 1.3.3.
Recipient [Optional]
A URI specifying the entity or location to which an attesting entity can present the assertion. For
example, this attribute might indicate that the assertion must be delivered to a particular network
endpoint in order to prevent an intermediary from redirecting it someplace else.
InResponseTo [Optional]
The ID of a SAML protocol message in response to which an attesting entity can present theassertion. For example, this attribute might be used to correlate the assertion to a SAML request that
resulted in its presentation.
Address [Optional]
The network address/location from which an attesting entity can present the assertion. For example,
this attribute might be used to bind the assertion to particular client addresses to prevent an attacker
from easily stealing and presenting the assertion from another location. IPv4 addresses SHOULD be
represented in the usual dotted-decimal format (e.g., "1.2.3.4"). IPv6 addresses SHOULD be
represented as defined by Section 2.2 of IETF RFC 3513 [RFC 3513] (e.g.,"FEDC:BA98:7654:3210:FEDC:BA98:7654:3210").

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 19 of 86

740

Arbitrary attributes

741
742
743
744
745
746
747

This complex type uses an <xs:anyAttribute> extension point to allow arbitrary namespacequalified XML attributes to be added to <SubjectConfirmationData> constructs without the needfor an explicit schema extension. This allows additional fields to be added as needed to supply
additional confirmation-related information. SAML extensions MUST NOT add local (non-namespacequalified) XML attributes or XML attributes qualified by a SAML-defined namespace to the
SubjectConfirmationDataType complex type or a derivation of it; such attributes are reserved for
future maintenance and enhancement of SAML itself.

748
749
750
751
752

Arbitrary elements
This complex type uses an <xs:any> extension point to allow arbitrary XML elements to be added to<SubjectConfirmationData> constructs without the need for an explicit schema extension. This
allows additional elements to be added as needed to supply additional confirmation-related
information.

753
754
755

Particular confirmation methods and profiles that make use of those methods MAY require the use of one
or more of the attributes defined within this complex type. For examples of how these attributes (andsubject confirmation in general) can be used, see the Profiles specification [SAMLProf].

756
757
758
759

Note that the time period specified by the optional NotBefore and NotOnOrAfter attributes, if present,
SHOULD fall within the overall assertion validity period as specified by the <Conditions> element's
NotBefore and NotOnOrAfter attributes. If both attributes are present, the value for NotBefore
MUST be less than (earlier than) the value for NotOnOrAfter.

760
761

The following schema fragment defines the <SubjectConfirmationData> element and its
SubjectConfirmationDataType complex type:

762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779

<element name="SubjectConfirmationData"
type="saml:SubjectConfirmationDataType"/><complexType name="SubjectConfirmationDataType" mixed="true"><complexContent><restriction base="anyType"><sequence><any namespace="##any" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/></sequence><attribute name="NotBefore" type="dateTime" use="optional"/><attribute name="NotOnOrAfter" type="dateTime" use="optional"/><attribute name="Recipient" type="anyURI" use="optional"/><attribute name="InResponseTo" type="NCName" use="optional"/><attribute name="Address" type="string" use="optional"/><anyAttribute namespace="##other" processContents="lax"/></restriction></complexContent></complexType>780

2.4.1.3 Complex Type KeyInfoConfirmationDataType

781
782
783
784
785

The KeyInfoConfirmationDataType complex type constrains a <SubjectConfirmationData>element to contain one or more <ds:KeyInfo> elements that identify cryptographic keys that are used insome way to authenticate an attesting entity. The particular confirmation method MUST define the exact
mechanism by which the confirmation data can be used. The optional attributes defined by the
SubjectConfirmationDataType complex type MAY also appear.

786
787

This complex type, or a type derived from it, SHOULD be used by any confirmation method that defines its
confirmation data in terms of the <ds:KeyInfo> element.

39
40

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 20 of 86

788
789
790

Note that in accordance with [XMLSig], each <ds:KeyInfo> element MUST identify a single
cryptographic key. Multiple keys MAY be identified with separate <ds:KeyInfo> elements, such as whena principal uses different keys to confirm itself to different relying parties.

791

The following schema fragment defines the KeyInfoConfirmationDataType complex type:

792
793
794
795
796
797
798
799
800

<complexType name="KeyInfoConfirmationDataType" mixed="false"><complexContent><restriction base="saml:SubjectConfirmationDataType"><sequence><element ref="ds:KeyInfo" maxOccurs="unbounded"/></sequence></restriction></complexContent></complexType>801

2.4.1.4 Example of a Key-Confirmed <Subject>

802
803
804
805

To illustrate the way in which the various elements and types fit together, below is an example of a
<Subject> element containing a name identifier and a subject confirmation based on proof of
possession of a key. Note the use of the KeyInfoConfirmationDataType to identify the confirmation data
syntax as being a <ds:KeyInfo> element:

806
807
808
809
810
811
812
813
814
815
816
817

<Subject><NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">scott@example.org</NameID><SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:holder-of-key"><SubjectConfirmationData xsi:type="saml:KeyInfoConfirmationDataType"><ds:KeyInfo><ds:KeyName>Scott's Key</ds:KeyName></ds:KeyInfo></SubjectConfirmationData></SubjectConfirmation></Subject>818

2.5 Conditions

819
820

This section defines the SAML constructs that place constraints on the acceptable use of SAML
assertions.

821

2.5.1 Element <Conditions>822

The <Conditions> element MAY contain the following elements and attributes:

823

NotBefore [Optional]

824
825
826
827
828
829
830
831
832
833

41
42

Specifies the earliest time instant at which the assertion is valid. The time value is encoded in UTC, as
described in Section 1.3.3.
NotOnOrAfter [Optional]
Specifies the time instant at which the assertion has expired. The time value is encoded in UTC, as
described in Section 1.3.3.
<Condition> [Any Number]
A condition of a type defined in an extension schema. An xsi:type attribute MUST be used toindicate the actual condition type.
<AudienceRestriction> [Any Number]Specifies that the assertion is addressed to a particular audience.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 21 of 86

834
835
836
837
838

<OneTimeUse> [Optional]
Specifies that the assertion SHOULD be used immediately and MUST NOT be retained for futureuse. Although the schema permits multiple occurrences, there MUST be at most one instance of
this element.
<ProxyRestriction> [Optional]

839
840
841
842

Specifies limitations that the asserting party imposes on relying parties that wish to subsequently act
as asserting parties themselves and issue assertions of their own on the basis of the information
contained in the original assertion. Although the schema permits multiple occurrences, there MUST
be at most one instance of this element.

843
844
845
846

Because the use of the xsi:type attribute would permit an assertion to contain more than one instanceof a SAML-defined subtype of ConditionsType (such as OneTimeUseType), the schema does not
explicitly limit the number of times particular conditions may be included. A particular type of condition
MAY define limits on such use, as shown above.

847
848

The following schema fragment defines the <Conditions> element and its ConditionsType complex
type:

849
850
851
852
853
854
855
856
857
858
859

<element name="Conditions" type="saml:ConditionsType"/><complexType name="ConditionsType"><choice minOccurs="0" maxOccurs="unbounded"><element ref="saml:Condition"/><element ref="saml:AudienceRestriction"/><element ref="saml:OneTimeUse"/><element ref="saml:ProxyRestriction"/></choice><attribute name="NotBefore" type="dateTime" use="optional"/><attribute name="NotOnOrAfter" type="dateTime" use="optional"/></complexType>860

2.5.1.1 General Processing Rules

861
862

If an assertion contains a <Conditions> element, then the validity of the assertion is dependent on the
sub-elements and attributes provided, using the following rules in the order shown below.

863
864
865

Note that an assertion that has condition validity status Valid may nonetheless be untrustworthy or invalid
for reasons such as not being well-formed or schema-valid, not being issued by a trustworthy SAML
authority, or not being authenticated by a trustworthy means.

866
867

Also note that some conditions may not directly impact the validity of the containing assertion (they always
evaluate to Valid), but may restrict the behavior of relying parties with respect to the use of the assertion.

868
869

1. If no sub-elements or attributes are supplied in the <Conditions> element, then the assertion isconsidered to be Valid with respect to condition processing.

870
871

2. If any sub-element or attribute of the <Conditions> element is determined to be invalid, then theassertion is considered to be Invalid.

872
873
874

3. If any sub-element or attribute of the <Conditions> element cannot be evaluated, or if an element isencountered that is not understood, then the validity of the assertion cannot be determined and isconsidered to be Indeterminate.

875
876

4. If all sub-elements and attributes of the <Conditions> element are determined to be Valid, then theassertion is considered to be Valid with respect to condition processing.

877
878

The first rule that applies terminates condition processing; thus a determination that an assertion is
Invalid takes precedence over that of Indeterminate.

43
44

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 22 of 86

879
880
881

An assertion that is determined to be Invalid or Indeterminate MUST be rejected by a relying party(within whatever context or profile it was being processed), just as if the assertion were malformed orotherwise unusable.

882

2.5.1.2 Attributes NotBefore and NotOnOrAfter

883
884
885

The NotBefore and NotOnOrAfter attributes specify time limits on the validity of the assertion within
the context of its profile(s) of use. They do not guarantee that the statements in the assertion will becorrect or accurate throughout the validity period.

886
887

The NotBefore attribute specifies the time instant at which the validity interval begins. The
NotOnOrAfter attribute specifies the time instant at which the validity interval has ended.

888
889
890
891
892
893
894

If the value for either NotBefore or NotOnOrAfter is omitted, then it is considered unspecified. If the
NotBefore attribute is unspecified (and if all other conditions that are supplied evaluate to Valid), thenthe assertion is Valid with respect to conditions at any time before the time instant specified by the
NotOnOrAfter attribute. If the NotOnOrAfter attribute is unspecified (and if all other conditions that aresupplied evaluate to Valid), the assertion is Valid with respect to conditions from the time instant specified
by the NotBefore attribute with no expiry. If neither attribute is specified (and if any other conditions thatare supplied evaluate to Valid), the assertion is Valid with respect to conditions at any time.

895
896

If both attributes are present, the value for NotBefore MUST be less than (earlier than) the value for
NotOnOrAfter.

897

2.5.1.3 Element <Condition>

898
899

The <Condition> element serves as an extension point for new conditions. Its ConditionAbstractTypecomplex type is abstract and is thus usable only as the base of a derived type.

900
901

The following schema fragment defines the <Condition> element and its ConditionAbstractTypecomplex type:

902
903

<element name="Condition" type="saml:ConditionAbstractType"/><complexType name="ConditionAbstractType" abstract="true"/>904

2.5.1.4 Elements <AudienceRestriction> and <Audience>

905
906
907
908
909

The <AudienceRestriction> element specifies that the assertion is addressed to one or more
specific audiences identified by <Audience> elements. Although a SAML relying party that is outside theaudiences specified is capable of drawing conclusions from an assertion, the SAML asserting party
explicitly makes no representation as to accuracy or trustworthiness to such a party. It contains thefollowing element:

910<Audience>

911
912
913

A URI reference that identifies an intended audience. The URI reference MAY identify a documentthat describes the terms and conditions of audience membership. It MAY also contain the unique
identifier URI from a SAML name identifier that describes a system entity (see Section 8.3.6).

914
915

The audience restriction condition evaluates to Valid if and only if the SAML relying party is a member of
one or more of the audiences specified.

916
917
918
919
920
921

The SAML asserting party cannot prevent a party to whom the assertion is disclosed from taking action on
the basis of the information provided. However, the <AudienceRestriction> element allows the
SAML asserting party to state explicitly that no warranty is provided to such a party in a machine- andhuman-readable form. While there can be no guarantee that a court would uphold such a warranty
exclusion in every circumstance, the probability of upholding the warranty exclusion is considerably
improved.

45
46

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 23 of 86

922
923
924
925

Note that multiple <AudienceRestriction> elements MAY be included in a single assertion, and each
MUST be evaluated independently. The effect of this requirement and the preceding definition is thatwithin a given condition, the audiences form a disjunction (an "OR") while multiple conditions form a
conjunction (an "AND").

926
927

The following schema fragment defines the <AudienceRestriction> element and its
AudienceRestrictionType complex type:

928
929
930
931
932
933
934
935
936
937
938
939

<element name="AudienceRestriction"
type="saml:AudienceRestrictionType"/><complexType name="AudienceRestrictionType"><complexContent><extension base="saml:ConditionAbstractType"><sequence><element ref="saml:Audience" maxOccurs="unbounded"/></sequence></extension></complexContent></complexType><element name="Audience" type="anyURI"/>

940

2.5.1.5 Element <OneTimeUse>

941
942
943
944
945

In general, relying parties may choose to retain assertions, or the information they contain in some otherform, for reuse. The <OneTimeUse> condition element allows an authority to indicate that the informationin the assertion is likely to change very soon and fresh information should be obtained for each use. An
example would be an assertion containing an <AuthzDecisionStatement> which was the result of apolicy which specified access control which was a function of the time of day.

946
947
948
949
950

If system clocks in a distributed environment could be precisely synchronized, then this requirement could
be met by careful use of the validity interval. However, since some clock skew between systems will
always be present and will be combined with possible transmission delays, there is no convenient way forthe issuer to appropriately limit the lifetime of an assertion without running a substantial risk that it will
already have expired before it arrives.

951
952
953
954
955

The <OneTimeUse> element indicates that the assertion SHOULD be used immediately by the relying
party and MUST NOT be retained for future use. Relying parties are always free to request a fresh
assertion for every use. However, implementations that choose to retain assertions for future use MUST
observe the <OneTimeUse> element. This condition is independent from the NotBefore and
NotOnOrAfter condition information.

956
957
958
959

To support the single use constraint, a relying party should maintain a cache of the assertions it has
processed containing such a condition. Whenever an assertion with this condition is processed, the cacheshould be checked to ensure that the same assertion has not been previously received and processed by
the relying party.

960
961

A SAML authority MUST NOT include more than one <OneTimeUse> element within a <Conditions>
element of an assertion.

962
963

For the purposes of determining the validity of the <Conditions> element, the <OneTimeUse> isconsidered to always be valid. That is, this condition does not affect validity but is a condition on use.

964
965

The following schema fragment defines the <OneTimeUse> element and its OneTimeUseType complex
type:

966
967
968
969
970
971

47
48

<element name="OneTimeUse" type="saml:OneTimeUseType"/><complexType name="OneTimeUseType"><complexContent><extension base="saml:ConditionAbstractType"/></complexContent></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 24 of 86

972

2.5.1.6 Element <ProxyRestriction>

973
974
975
976

Specifies limitations that the asserting party imposes on relying parties that in turn wish to act as asserting
parties and issue subsequent assertions of their own on the basis of the information contained in theoriginal assertion. A relying party acting as an asserting party MUST NOT issue an assertion that itself
violates the restrictions specified in this condition on the basis of an assertion containing such a condition.

977

The <ProxyRestriction> element contains the following elements and attributes:

978Count [Optional]

979
980
981

Specifies the maximum number of indirections that the asserting party permits to exist between thisassertion and an assertion which has ultimately been issued on the basis of it.
<Audience> [Zero or More]

982
983

Specifies the set of audiences to whom the asserting party permits new assertions to be issued on
the basis of this assertion.

984
985
986

A Count value of zero indicates that a relying party MUST NOT issue an assertion to another relying partyon the basis of this assertion. If greater than zero, any assertions so issued MUST themselves contain a<ProxyRestriction> element with a Count value of at most one less than this value.

987
988
989
990
991

If no <Audience> elements are specified, then no audience restrictions are imposed on the relying
parties to whom subsequent assertions can be issued. Otherwise, any assertions so issued MUST
themselves contain an <AudienceRestriction> element with at least one of the <Audience>elements present in the previous <ProxyRestriction> element, and no <Audience> elements
present that were not in the previous <ProxyRestriction> element.

992
993

A SAML authority MUST NOT include more than one <ProxyRestriction> element within a<Conditions> element of an assertion.

994
995
996

For the purposes of determining the validity of the <Conditions> element, the <ProxyRestriction>
condition is considered to always be valid. That is, this condition does not affect validity but is a condition
on use.

997
998

The following schema fragment defines the <ProxyRestriction> element and its
ProxyRestrictionType complex type:

999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010

<element name="ProxyRestriction" type="saml:ProxyRestrictionType"/><complexType name="ProxyRestrictionType"><complexContent><extension base="saml:ConditionAbstractType"><sequence><element ref="saml:Audience" minOccurs="0"
maxOccurs="unbounded"/></sequence><attribute name="Count" type="nonNegativeInteger" use="optional"/></extension></complexContent></complexType>

1011

2.6 Advice

1012
1013

This section defines the SAML constructs that contain additional information about an assertion that an
asserting party wishes to provide to a relying party.

49
50

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 25 of 86

1014

2.6.1 Element <Advice>

1015
1016
1017

The <Advice> element contains any additional information that the SAML authority wishes to provide.
This information MAY be ignored by applications without affecting either the semantics or the validity of
the assertion.

1018
1019
1020

The <Advice> element contains a mixture of zero or more <Assertion>, <EncryptedAssertion>,<AssertionIDRef>, and <AssertionURIRef> elements, and namespace-qualified elements inother non-SAML namespaces.

1021

Following are some potential uses of the <Advice> element:

1022
1023

• Include evidence supporting the assertion claims to be cited, either directly (through incorporating
the claims) or indirectly (by reference to the supporting assertions).

1024• State a proof of the assertion claims.

1025• Specify the timing and distribution points for updates to the assertion.

1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036

The following schema fragment defines the <Advice> element and its AdviceType complex type:<element name="Advice" type="saml:AdviceType"/><complexType name="AdviceType"><choice minOccurs="0" maxOccurs="unbounded"><element ref="saml:AssertionIDRef"/><element ref="saml:AssertionURIRef"/><element ref="saml:Assertion"/><element ref="saml:EncryptedAssertion"/><any namespace="##other" processContents="lax"/></choice></complexType>1037

2.7 Statements

1038

The following sections define the SAML constructs that contain statement information.

1039

2.7.1 Element <Statement>

1040
1041
1042

The <Statement> element is an extension point that allows other assertion-based applications to reuse
the SAML assertion framework. SAML itself derives its core statements from this extension point. Its
StatementAbstractType complex type is abstract and is thus usable only as the base of a derived type.

1043
1044

The following schema fragment defines the <Statement> element and its StatementAbstractTypecomplex type:

1045
1046

<element name="Statement" type="saml:StatementAbstractType"/><complexType name="StatementAbstractType" abstract="true"/>1047

2.7.2 Element <AuthnStatement>

1048
1049
1050

The <AuthnStatement> element describes a statement by the SAML authority asserting that theassertion subject was authenticated by a particular means at a particular time. Assertions containing<AuthnStatement> elements MUST contain a <Subject> element.

1051
1052

It is of type AuthnStatementType, which extends StatementAbstractType with the addition of thefollowing elements and attributes:

1053
1054

51
52

Note: The <AuthorityBinding> element and its corresponding type were removed
from <AuthnStatement> for V2.0 of SAML.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 26 of 86

1055

AuthnInstant [Required]
Specifies the time at which the authentication took place. The time value is encoded in UTC, as
described in Section 1.3.3.

1056
1057
1058

SessionIndex [Optional]
Specifies the index of a particular session between the principal identified by the subject and theauthenticating authority.

1059
1060
1061

SessionNotOnOrAfter [Optional]
Specifies a time instant at which the session between the principal identified by the subject and the
SAML authority issuing this statement MUST be considered ended. The time value is encoded in
UTC, as described in Section 1.3.3. There is no required relationship between this attribute and a
NotOnOrAfter condition attribute that may be present in the assertion.

1062
1063
1064
1065
1066

<SubjectLocality> [Optional]
Specifies the DNS domain name and IP address for the system from which the assertion subject wasapparently authenticated.

1067
1068
1069

<AuthnContext> [Required]

1070
1071
1072
1073

The context used by the authenticating authority up to and including the authentication event thatyielded this statement. Contains an authentication context class reference, an authentication context
declaration or declaration reference, or both. See the Authentication Context specification[SAMLAuthnCxt] for a full description of authentication context information.

1074
1075
1076
1077
1078

In general, any string value MAY be used as a SessionIndex value. However, when privacy is aconsideration, care must be taken to ensure that the SessionIndex value does not invalidate otherprivacy mechanisms. Accordingly, the value SHOULD NOT be usable to correlate activity by a principal
across different session participants. Two solutions that achieve this goal are provided below and are
RECOMMENDED:

1079
1080
1081
1082
1083
1084

•

Use small positive integers (or reoccurring constants in a list) for the SessionIndex. The SAML
authority SHOULD choose the range of values such that the cardinality of any one integer will be
sufficiently high to prevent a particular principal's actions from being correlated across multiple session
participants. The SAML authority SHOULD choose values for SessionIndex randomly from within
this range (except when required to ensure unique values for subsequent statements given to thesame session participant but as part of a distinct session).

1085

•

Use the enclosing assertion's ID value in the SessionIndex.

1086
1087

The following schema fragment defines the <AuthnStatement> element and its AuthnStatementTypecomplex type:

1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102

53
54

<element name="AuthnStatement" type="saml:AuthnStatementType"/><complexType name="AuthnStatementType"><complexContent><extension base="saml:StatementAbstractType"><sequence><element ref="saml:SubjectLocality" minOccurs="0"/><element ref="saml:AuthnContext"/></sequence><attribute name="AuthnInstant" type="dateTime" use="required"/><attribute name="SessionIndex" type="string" use="optional"/><attribute name="SessionNotOnOrAfter" type="dateTime"use="optional"/></extension></complexContent></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 27 of 86

1103

2.7.2.1 Element <SubjectLocality>

1104
1105

The <SubjectLocality> element specifies the DNS domain name and IP address for the system fromwhich the assertion subject was authenticated. It has the following attributes:

1106

Address [Optional]

1107
1108
1109
1110
1111
1112

The network address of the system from which the principal identified by the subject wasauthenticated. IPv4 addresses SHOULD be represented in dotted-decimal format (e.g., "1.2.3.4").
IPv6 addresses SHOULD be represented as defined by Section 2.2 of IETF RFC 3513 [RFC 3513](e.g., "FEDC:BA98:7654:3210:FEDC:BA98:7654:3210").
DNSName [Optional]
The DNS name of the system from which the principal identified by the subject was authenticated.

1113
1114

This element is entirely advisory, since both of these fields are quite easily “spoofed,” but may be useful
information in some applications.

1115
1116

The following schema fragment defines the <SubjectLocality> element and its SubjectLocalityTypecomplex type:

1117
1118
1119
1120
1121

<element name="SubjectLocality" type="saml:SubjectLocalityType"/><complexType name="SubjectLocalityType"><attribute name="Address" type="string" use="optional"/><attribute name="DNSName" type="string" use="optional"/></complexType>1122

2.7.2.2 Element <AuthnContext>

1123
1124
1125

The <AuthnContext> element specifies the context of an authentication event. The element can contain
an authentication context class reference, an authentication context declaration or declaration reference,or both. Its complex AuthnContextType has the following elements:

1126<AuthnContextClassRef> [Optional]

1127
1128
1129
1130
1131
1132
1133
1134
1135
1136

A URI reference identifying an authentication context class that describes the authentication context
declaration that follows.
<AuthnContextDecl> or <AuthnContextDeclRef> [Optional]
Either an authentication context declaration provided by value, or a URI reference that identifies sucha declaration. The URI reference MAY directly resolve into an XML document containing thereferenced declaration.
<AuthenticatingAuthority> [Zero or More]
Zero or more unique identifiers of authentication authorities that were involved in the authentication of
the principal (not including the assertion issuer, who is presumed to have been involved without being
explicitly named here).

1137
1138

See the Authentication Context specification [SAMLAuthnCxt] for a full description of authentication
context information.

1139
1140

The following schema fragment defines the <AuthnContext> element and its AuthnContextTypecomplex type:

1141
1142
1143
1144
1145
1146
1147

55
56

<element name="AuthnContext" type="saml:AuthnContextType"/><complexType name="AuthnContextType"><sequence><choice><sequence><element ref="saml:AuthnContextClassRef"/><choice minOccurs="0">saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 28 of 86

1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164

<element ref="saml:AuthnContextDecl"/><element ref="saml:AuthnContextDeclRef"/></choice></sequence><choice><element ref="saml:AuthnContextDecl"/><element ref="saml:AuthnContextDeclRef"/></choice></choice><element ref="saml:AuthenticatingAuthority" minOccurs="0"
maxOccurs="unbounded"/></sequence></complexType><element name="AuthnContextClassRef" type="anyURI"/><element name="AuthnContextDeclRef" type="anyURI"/><element name="AuthnContextDecl" type="anyType"/><element name="AuthenticatingAuthority" type="anyURI"/>

1165

2.7.3 Element <AttributeStatement>

1166
1167
1168

The <AttributeStatement> element describes a statement by the SAML authority asserting that theassertion subject is associated with the specified attributes. Assertions containing<AttributeStatement> elements MUST contain a <Subject> element.

1169
1170

It is of type AttributeStatementType, which extends StatementAbstractType with the addition of thefollowing elements:

1171<Attribute> or <EncryptedAttribute> [One or More]

1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186

The <Attribute> element specifies an attribute of the assertion subject. An encrypted SAML
attribute may be included with the <EncryptedAttribute> element.
The following schema fragment defines the <AttributeStatement> element and its
AttributeStatementType complex type:<element name="AttributeStatement" type="saml:AttributeStatementType"/><complexType name="AttributeStatementType"><complexContent><extension base="saml:StatementAbstractType"><choice maxOccurs="unbounded"><element ref="saml:Attribute"/><element ref="saml:EncryptedAttribute"/></choice></extension></complexContent></complexType>1187

2.7.3.1 Element <Attribute>

1188
1189
1190
1191
1192

The <Attribute> element identifies an attribute by name and optionally includes its value(s). It has the
AttributeType complex type. It is used within an attribute statement to express particular attributes andvalues associated with an assertion subject, as described in the previous section. It is also used in an
attribute query to request that the values of specific SAML attributes be returned (see Section 3.3.2.3 formore information). The <Attribute> element contains the following XML attributes:

1193

Name [Required]

1194
1195
1196

57
58

The name of the attribute.
NameFormat [Optional]
A URI reference representing the classification of the attribute name for purposes of interpreting thesaml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 29 of 86

1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212

name. See Section 8.2 for some URI references that MAY be used as the value of the NameFormat
attribute and their associated descriptions and processing rules. If no NameFormat value is provided,
the identifier urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified (see Section
8.2.1) is in effect.
FriendlyName [Optional]
A string that provides a more human-readable form of the attribute's name, which may be useful incases in which the actual Name is complex or opaque, such as an OID or a UUID. This attribute's
value MUST NOT be used as a basis for formally identifying SAML attributes.
Arbitrary attributes
This complex type uses an <xs:anyAttribute> extension point to allow arbitrary XML attributes tobe added to <Attribute> constructs without the need for an explicit schema extension. This allows
additional fields to be added as needed to supply additional parameters to be used, for example, in an
attribute query. SAML extensions MUST NOT add local (non-namespace-qualified) XML attributes or
XML attributes qualified by a SAML-defined namespace to the AttributeType complex type or aderivation of it; such attributes are reserved for future maintenance and enhancement of SAML itself.
<AttributeValue> [Any Number]

1213
1214
1215
1216
1217

Contains a value of the attribute. If an attribute contains more than one discrete value, it is
RECOMMENDED that each value appear in its own <AttributeValue> element. If more thanone <AttributeValue> element is supplied for an attribute, and any of the elements have adatatype assigned through xsi:type, then all of the <AttributeValue> elements must havethe identical datatype assigned.

1218
1219
1220
1221
1222

The meaning of an <Attribute> element that contains no <AttributeValue> elements depends on
its context. Within an <AttributeStatement>, if the SAML attribute exists but has no values, then the<AttributeValue> element MUST be omitted. Within a <samlp:AttributeQuery>, the absence ofvalues indicates that the requester is interested in any or all of the named attribute's values (see also
Section 3.3.2.3).

1223
1224

Any other uses of the <Attribute> element by profiles or other specifications MUST define thesemantics of specifying or omitting <AttributeValue> elements.

1225

The following schema fragment defines the <Attribute> element and its AttributeType complex type:

1226
1227
1228
1229
1230
1231
1232
1233
1234
1235

<element name="Attribute" type="saml:AttributeType"/><complexType name="AttributeType"><sequence><element ref="saml:AttributeValue" minOccurs="0" maxOccurs="unbounded"/></sequence><attribute name="Name" type="string" use="required"/><attribute name="NameFormat" type="anyURI" use="optional"/><attribute name="FriendlyName" type="string" use="optional"/><anyAttribute namespace="##other" processContents="lax"/></complexType>

1236

2.7.3.1.1 Element <AttributeValue>

1237
1238

The <AttributeValue> element supplies the value of a specified SAML attribute. It is of thexs:anyType type, which allows any well-formed XML to appear as the content of the element.

1239
1240
1241
1242

If the data content of an <AttributeValue> element is of an XML Schema simple type (such as
xs:integer or xs:string), the datatype MAY be declared explicitly by means of an xsi:type declarationin the <AttributeValue> element. If the attribute value contains structured data, the necessary data
elements MAY be defined in an extension schema.

59
60

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 30 of 86

1243
1244
1245

Note: Specifying a datatype other than an XML Schema simple type on<AttributeValue> using xsi:type will require the presence of the extension schemathat defines the datatype in order for schema processing to proceed.

1246
1247
1248
1249

If a SAML attribute includes an empty value, such as the empty string, the corresponding<AttributeValue> element MUST be empty (generally this is serialized as <AttributeValue/>).
This overrides the requirement in Section 1.3.1 that string values in SAML content contain at least one
non-whitespace character.

1250
1251

If a SAML attribute includes a "null" value, the corresponding <AttributeValue> element MUST be
empty and MUST contain the reserved xsi:nil XML attribute with a value of "true" or "1".

1252

The following schema fragment defines the <AttributeValue> element:

1253<element name="AttributeValue" type="anyType" nillable="true"/>1254

2.7.3.2 Element <EncryptedAttribute>

1255
1256
1257

The <EncryptedAttribute> element represents a SAML attribute in encrypted fashion, as defined by
the XML Encryption Syntax and Processing specification [XMLEnc]. The <EncryptedAttribute>element contains the following elements:

1258<xenc:EncryptedData> [Required]

1259
1260
1261
1262
1263

The encrypted content and associated encryption details, as defined by the XML Encryption
Syntax and Processing specification [XMLEnc]. The Type attribute SHOULD be present and, if
present, MUST contain a value of http://www.w3.org/2001/04/xmlenc#Element. The
encrypted content MUST contain an element that has a type of or derived from AttributeType.
<xenc:EncryptedKey> [Zero or More]

1264
1265
1266
1267

Wrapped decryption keys, as defined by [XMLEnc]. Each wrapped key SHOULD include a
Recipient attribute that specifies the entity for whom the key has been encrypted. The value of
the Recipient attribute SHOULD be the URI identifier of a system entity with a SAML nameidentifier, as defined by Section 8.3.6.

1268
1269

Encrypted attributes are intended as a confidentiality protection when the plain-text value passes throughan intermediary.

1270

The following schema fragment defines the <EncryptedAttribute> element:

1271

1272

<element name="EncryptedAttribute" type="saml:EncryptedElementType"/>2.7.4 Element <AuthzDecisionStatement>

1273
1274
1275
1276

Note: The <AuthzDecisionStatement> feature has been frozen as of SAML V2.0,
with no future enhancements planned. Users who require additional functionality may
want to consider the eXtensible Access Control Markup Language [XACML], which offers
enhanced authorization decision features.

1277
1278
1279
1280

The <AuthzDecisionStatement> element describes a statement by the SAML authority asserting thata request for access by the assertion subject to the specified resource has resulted in the specified
authorization decision on the basis of some optionally specified evidence. Assertions containing<AuthzDecisionStatement> elements MUST contain a <Subject> element.

1281
1282
1283

The resource is identified by means of a URI reference. In order for the assertion to be interpreted
correctly and securely, the SAML authority and SAML relying party MUST interpret each URI reference ina consistent manner. Failure to achieve a consistent URI reference interpretation can result in different

61
62

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 31 of 86

1284
1285

authorization decisions depending on the encoding of the resource URI reference. Rules for normalizing
URI references are to be found in IETF RFC 2396 [RFC 2396] Section 6:

1286
1287
1288
1289
1290

In general, the rules for equivalence and definition of a normal form, if any, are scheme
dependent. When a scheme uses elements of the common syntax, it will also use the common
syntax equivalence rules, namely that the scheme and hostname are case insensitive and a URL
with an explicit ":port", where the port is the default for the scheme, is equivalent to one where
the port is elided.

1291
1292

To avoid ambiguity resulting from variations in URI encoding, SAML system entities SHOULD employ the
URI normalized form wherever possible as follows:

1293• SAML authorities SHOULD encode all resource URI references in normalized form.

1294• Relying parties SHOULD convert resource URI references to normalized form prior to processing.

1295
1296
1297
1298

Inconsistent URI reference interpretation can also result from differences between the URI reference
syntax and the semantics of an underlying file system. Particular care is required if URI references are
employed to specify an access control policy language. The following security conditions SHOULD besatisfied by the system which employs SAML assertions:

1299
1300
1301

• Parts of the URI reference syntax are case sensitive. If the underlying file system is case insensitive,a requester SHOULD NOT be able to gain access to a denied resource by changing the case of apart of the resource URI reference.

1302
1303
1304

• Many file systems support mechanisms such as logical paths and symbolic links, which allow users
to establish logical equivalences between file system entries. A requester SHOULD NOT be able togain access to a denied resource by creating such an equivalence.

1305
1306

The <AuthzDecisionStatement> element is of type AuthzDecisionStatementType, which extends
StatementAbstractType with the addition of the following elements and attributes:

1307

Resource [Required]

1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330

63
64

A URI reference identifying the resource to which access authorization is sought. This attribute MAY
have the value of the empty URI reference (""), and the meaning is defined to be "the start of thecurrent document", as specified by IETF RFC 2396 [RFC 2396] Section 4.2.
Decision [Required]
The decision rendered by the SAML authority with respect to the specified resource. The value is of
the DecisionType simple type.
<Action> [One or more]
The set of actions authorized to be performed on the specified resource.
<Evidence> [Optional]
A set of assertions that the SAML authority relied on in making the decision.
The following schema fragment defines the <AuthzDecisionStatement> element and its
AuthzDecisionStatementType complex type:<element name="AuthzDecisionStatement"
type="saml:AuthzDecisionStatementType"/><complexType name="AuthzDecisionStatementType"><complexContent><extension base="saml:StatementAbstractType"><sequence><element ref="saml:Action" maxOccurs="unbounded"/><element ref="saml:Evidence" minOccurs="0"/></sequence><attribute name="Resource" type="anyURI" use="required"/><attribute name="Decision" type="saml:DecisionType" use="required"/>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 32 of 86

1331
1332
1333

</extension></complexContent></complexType>1334

2.7.4.1 Simple Type DecisionType

1335
1336

The DecisionType simple type defines the possible values to be reported as the status of an
authorization decision statement.

1337

Permit

1338
1339
1340
1341
1342

The specified action is permitted.
Deny
The specified action is denied.
Indeterminate
The SAML authority cannot determine whether the specified action is permitted or denied.

1343
1344
1345
1346

The Indeterminate decision value is used in situations where the SAML authority requires the ability toprovide an affirmative statement but where it is not able to issue a decision. Additional information as to
the reason for the refusal or inability to provide a decision MAY be returned as <StatusDetail>elements in the enclosing <Response>.

1347

The following schema fragment defines the DecisionType simple type:

1348
1349
1350
1351
1352
1353
1354

<simpleType name="DecisionType"><restriction base="string"><enumeration value="Permit"/><enumeration value="Deny"/><enumeration value="Indeterminate"/></restriction></simpleType>1355

2.7.4.2 Element <Action>

1356
1357
1358

The <Action> element specifies an action on the specified resource for which permission is sought. Its
string-data content provides the label for an action sought to be performed on the specified resource, andit has the following attribute:

1359

Namespace [Optional]

1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372

65
66

A URI reference representing the namespace in which the name of the specified action is to beinterpreted. If this element is absent, the namespace
urn:oasis:names:tc:SAML:1.0:action:rwedc-negation specified in Section 8.1.2 is ineffect.
The following schema fragment defines the <Action> element and its ActionType complex type:<element name="Action" type="saml:ActionType"/><complexType name="ActionType"><simpleContent><extension base="string"><attribute name="Namespace" type="anyURI" use="required"/></extension></simpleContent></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 33 of 86

1373

2.7.4.3 Element <Evidence>

1374
1375
1376

The <Evidence> element contains one or more assertions or assertion references that the SAML
authority relied on in issuing the authorization decision. It has the EvidenceType complex type. It contains
a mixture of one or more of the following elements:

1377<AssertionIDRef> [Any number]

1378
1379
1380
1381

Specifies an assertion by reference to the value of the assertion’s ID attribute.
<AssertionURIRef> [Any number]Specifies an assertion by means of a URI reference.
<Assertion> [Any number]

1382

Specifies an assertion by value.

1383<EncryptedAssertion> [Any number]

1384

Specifies an encrypted assertion by value.

1385
1386
1387
1388
1389

Providing an assertion as evidence MAY affect the reliance agreement between the SAML relying party
and the SAML authority making the authorization decision. For example, in the case that the SAML relying
party presented an assertion to the SAML authority in a request, the SAML authority MAY use that
assertion as evidence in making its authorization decision without endorsing the <Evidence> element’s
assertion as valid either to the relying party or any other third party.

1390

The following schema fragment defines the <Evidence> element and its EvidenceType complex type:

1391
1392
1393
1394
1395
1396
1397
1398
1399

67
68

<element name="Evidence" type="saml:EvidenceType"/><complexType name="EvidenceType"><choice maxOccurs="unbounded"><element ref="saml:AssertionIDRef"/><element ref="saml:AssertionURIRef"/><element ref="saml:Assertion"/><element ref="saml:EncryptedAssertion"/></choice></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 34 of 86

1400

3 SAML Protocols

1401
1402
1403
1404
1405

SAML protocol messages can be generated and exchanged using a variety of protocols. The SAML
bindings specification [SAMLBind] describes specific means of transporting protocol messages using
existing widely deployed transport protocols. The SAML profile specification [SAMLProf] describes anumber of applications of the protocols defined in this section together with additional processing rules,
restrictions, and requirements that facilitate interoperability.

1406
1407
1408

Specific SAML request and response messages derive from common types. The requester sends anelement derived from RequestAbstractType to a SAML responder, and the responder generates anelement adhering to or deriving from StatusResponseType, as shown in Figure 1.

1409

RequestAbstractType

1411

Process Request

StatusResponseType

Figure 1: SAML Request-Response Protocol

1412
1413

In certain cases, when permitted by profiles, a SAML response MAY be generated and sent without the
responder having received a corresponding request.

1414

The protocols defined by SAML achieve the following actions:

1415
1416

• Returning one or more requested assertions. This can occur in response to either a direct request
for specific assertions or a query for assertions that meet particular criteria.

1417• Performing authentication on request and returning the corresponding assertion

1418• Registering a name identifier or terminating a name registration on request

1419• Retrieving a protocol message that has been requested by means of an artifact

1420
1421

• Performing a near-simultaneous logout of a collection of related sessions (“single logout”) on
request1422• Providing a name identifier mapping on request

1423
1424
1425

Throughout this section, text descriptions of elements and types in the SAML protocol namespace are notshown with the conventional namespace prefix samlp:. For clarity, text descriptions of elements andtypes in the SAML assertion namespace are indicated with the conventional namespace prefix saml:.

1426

3.1 Schema Header and Namespace Declarations

1427
1428

The following schema fragment defines the XML namespaces and other header information for the
protocol schema:

1429
1430
1431
1432
1433
1434
1435
1436
1437
1438

69
70

<schematargetNamespace="urn:oasis:names:tc:SAML:2.0:protocol"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
elementFormDefault="unqualified"attributeFormDefault="unqualified"
blockDefault="substitution"version="2.0">

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 35 of 86

1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458

<import namespace="urn:oasis:names:tc:SAML:2.0:assertion"
schemaLocation="saml-schema-assertion-2.0.xsd"/><import namespace="http://www.w3.org/2000/09/xmldsig#"
schemaLocation="http://www.w3.org/TR/2002/REC-xmldsig-core20020212/xmldsig-core-schema.xsd"/><annotation><documentation>
Document identifier: saml-schema-protocol-2.0
Location: http://docs.oasis-open.org/security/saml/v2.0/
Revision history:
V1.0 (November, 2002):
Initial Standard Schema.
V1.1 (September, 2003):
Updates within the same V1.0 namespace.
V2.0 (March, 2005):
New protocol schema based in a SAML V2.0 namespace.
</documentation></annotation>…
</schema>1459

3.2 Requests and Responses

1460
1461

The following sections define the SAML constructs and basic requirements that underlie all of the request
and response messages used in SAML protocols.

1462

3.2.1 Complex Type RequestAbstractType

1463
1464

All SAML requests are of types that are derived from the abstract RequestAbstractType complex type.
This type defines common attributes and elements that are associated with all SAML requests:

1465
1466

Note: The <RespondWith> element has been removed from RequestAbstractType
for V2.0 of SAML.

1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485

71
72

ID [Required]
An identifier for the request. It is of type xs:ID and MUST follow the requirements specified in Section
1.3.4 for identifier uniqueness. The values of the ID attribute in a request and the InResponseTo
attribute in the corresponding response MUST match.
Version [Required]
The version of this request. The identifier for the version of SAML defined in this specification is "2.0".
SAML versioning is discussed in Section 4.
IssueInstant [Required]
The time instant of issue of the request. The time value is encoded in UTC, as described in Section
1.3.3.
Destination [Optional]
A URI reference indicating the address to which this request has been sent. This is useful to prevent
malicious forwarding of requests to unintended recipients, a protection that is required by some
protocol bindings. If it is present, the actual recipient MUST check that the URI reference identifies thelocation at which the message was received. If it does not, the request MUST be discarded. Some
protocol bindings may require the use of this attribute (see [SAMLBind]).
Consent [Optional]
Indicates whether or not (and under what conditions) consent has been obtained from a principal in
the sending of this request. See Section 8.4 for some URI references that MAY be used as the valuesaml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 36 of 86

1486
1487
1488
1489
1490
1491
1492
1493
1494
1495

of the Consent attribute and their associated descriptions. If no Consent value is provided, theidentifier urn:oasis:names:tc:SAML:2.0:consent:unspecified (see Section 8.4.1) is ineffect.
<saml:Issuer> [Optional]
Identifies the entity that generated the request message. (For more information on this element, see
Section 2.2.5.)<ds:Signature> [Optional]
An XML Signature that authenticates the requester and provides message integrity, as described
below and in Section 5.
<Extensions> [Optional]

1496
1497
1498
1499
1500

This extension point contains optional protocol message extension elements that are agreed on
between the communicating parties. No extension schema is required in order to make use of thisextension point, and even if one is provided, the lax validation setting does not impose a requirement
for the extension to be valid. SAML extension elements MUST be namespace-qualified in a nonSAML-defined namespace.

1501
1502
1503
1504

Depending on the requirements of particular protocols or profiles, a SAML requester may often need toauthenticate itself, and message integrity may often be required. Authentication and message integrity
MAY be provided by mechanisms provided by the protocol binding (see [SAMLBind]). The SAML request
MAY be signed, which provides both authentication of the requester and message integrity.

1505
1506
1507
1508
1509
1510

If such a signature is used, then the <ds:Signature> element MUST be present, and the SAML
responder MUST verify that the signature is valid (that is, that the message has not been tampered with)in accordance with [XMLSig]. If it is invalid, then the responder MUST NOT rely on the contents of therequest and SHOULD respond with an error. If it is valid, then the responder SHOULD evaluate thesignature to determine the identity and appropriateness of the signer and may continue to process therequest or respond with an error (if the request is invalid for some other reason).

1511
1512

If a Consent attribute is included and the value indicates that some form of principal consent has beenobtained, then the request SHOULD be signed.

1513
1514
1515
1516

If a SAML responder deems a request to be invalid according to SAML syntax or processing rules, then if
it responds, it MUST return a SAML response message with a <StatusCode> element with the value
urn:oasis:names:tc:SAML:2.0:status:Requester. In some cases, for example during asuspected denial-of-service attack, not responding at all may be warranted.

1517

The following schema fragment defines the RequestAbstractType complex type:

1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535

73
74

<complexType name="RequestAbstractType" abstract="true"><sequence><element ref="saml:Issuer" minOccurs="0"/><element ref="ds:Signature" minOccurs="0"/><element ref="samlp:Extensions" minOccurs="0"/></sequence><attribute name="ID" type="ID" use="required"/><attribute name="Version" type="string" use="required"/><attribute name="IssueInstant" type="dateTime" use="required"/><attribute name="Destination" type="anyURI" use="optional"/><attribute name="Consent" type="anyURI" use="optional"/></complexType><element name="Extensions" type="samlp:ExtensionsType"/><complexType name="ExtensionsType"><sequence><any namespace="##other" processContents="lax" maxOccurs="unbounded"/></sequence></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 37 of 86

1536

3.2.2 Complex Type StatusResponseType

1537
1538

All SAML responses are of types that are derived from the StatusResponseType complex type. This typedefines common attributes and elements that are associated with all SAML responses:

1539

ID [Required]

1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579

75
76

An identifier for the response. It is of type xs:ID, and MUST follow the requirements specified in
Section 1.3.4 for identifier uniqueness.
InResponseTo [Optional]
A reference to the identifier of the request to which the response corresponds, if any. If the response
is not generated in response to a request, or if the ID attribute value of a request cannot be
determined (for example, the request is malformed), then this attribute MUST NOT be present.
Otherwise, it MUST be present and its value MUST match the value of the corresponding request's
ID attribute.
Version [Required]
The version of this response. The identifier for the version of SAML defined in this specification is"2.0". SAML versioning is discussed in Section 4.
IssueInstant [Required]
The time instant of issue of the response. The time value is encoded in UTC, as described in Section
1.3.3.
Destination [Optional]
A URI reference indicating the address to which this response has been sent. This is useful to prevent
malicious forwarding of responses to unintended recipients, a protection that is required by some
protocol bindings. If it is present, the actual recipient MUST check that the URI reference identifies thelocation at which the message was received. If it does not, the response MUST be discarded. Some
protocol bindings may require the use of this attribute (see [SAMLBind]).
Consent [Optional]
Indicates whether or not (and under what conditions) consent has been obtained from a principal in
the sending of this response. See Section 8.4 for some URI references that MAY be used as the valueof the Consent attribute and their associated descriptions. If no Consent value is provided, theidentifier urn:oasis:names:tc:SAML:2.0:consent:unspecified (see Section 8.4.1) is ineffect.
<saml:Issuer> [Optional]
Identifies the entity that generated the response message. (For more information on this element, see
Section 2.2.5.)<ds:Signature> [Optional]
An XML Signature that authenticates the responder and provides message integrity, as described
below and in Section 5.
<Extensions> [Optional]
This extension point contains optional protocol message extension elements that are agreed on
between the communicating parties. . No extension schema is required in order to make use of thisextension point, and even if one is provided, the lax validation setting does not impose a requirement
for the extension to be valid. SAML extension elements MUST be namespace-qualified in a nonSAML-defined namespace.
<Status> [Required]A code representing the status of the corresponding request.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 38 of 86

1580
1581
1582
1583

Depending on the requirements of particular protocols or profiles, a SAML responder may often need toauthenticate itself, and message integrity may often be required. Authentication and message integrity
MAY be provided by mechanisms provided by the protocol binding (see [SAMLBind]). The SAML
response MAY be signed, which provides both authentication of the responder and message integrity.

1584
1585
1586
1587
1588
1589

If such a signature is used, then the <ds:Signature> element MUST be present, and the SAML
requester receiving the response MUST verify that the signature is valid (that is, that the message has notbeen tampered with) in accordance with [XMLSig]. If it is invalid, then the requester MUST NOT rely on
the contents of the response and SHOULD treat it as an error. If it is valid, then the requester SHOULD
evaluate the signature to determine the identity and appropriateness of the signer and may continue toprocess the response as it deems appropriate.

1590
1591

If a Consent attribute is included and the value indicates that some form of principal consent has beenobtained, then the response SHOULD be signed.

1592

The following schema fragment defines the StatusResponseType complex type:

1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606

<complexType name="StatusResponseType"><sequence><element ref="saml:Issuer" minOccurs="0"/><element ref="ds:Signature" minOccurs="0"/><element ref="samlp:Extensions" minOccurs="0"/><element ref="samlp:Status"/></sequence><attribute name="ID" type="ID" use="required"/><attribute name="InResponseTo" type="NCName" use="optional"/><attribute name="Version" type="string" use="required"/><attribute name="IssueInstant" type="dateTime" use="required"/><attribute name="Destination" type="anyURI" use="optional"/><attribute name="Consent" type="anyURI" use="optional"/></complexType>1607

3.2.2.1 Element <Status>

1608

The <Status> element contains the following elements:

1609<StatusCode> [Required]

1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623

A code representing the status of the activity carried out in response to the corresponding request.
<StatusMessage> [Optional]
A message which MAY be returned to an operator.
<StatusDetail> [Optional]
Additional information concerning the status of the request.
The following schema fragment defines the <Status> element and its StatusType complex type:<element name="Status" type="samlp:StatusType"/><complexType name="StatusType"><sequence><element ref="samlp:StatusCode"/><element ref="samlp:StatusMessage" minOccurs="0"/><element ref="samlp:StatusDetail" minOccurs="0"/></sequence></complexType>

1624

3.2.2.2 Element <StatusCode>

1625
1626

The <StatusCode> element specifies a code or a set of nested codes representing the status of thecorresponding request. The <StatusCode> element has the following element and attribute:

77
78

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 39 of 86

1627
1628
1629
1630
1631
1632
1633

Value [Required]
The status code value. This attribute contains a URI reference. The value of the topmost<StatusCode> element MUST be from the top-level list provided in this section.
<StatusCode> [Optional]
A subordinate status code that provides more specific information on an error condition. Note that
responders MAY omit subordinate status codes in order to prevent attacks that seek to probe for
additional information by intentionally presenting erroneous requests.

1634

The permissible top-level <StatusCode> values are as follows:1635

urn:oasis:names:tc:SAML:2.0:status:Success

1636
1637
1638
1639
1640
1641
1642
1643
1644
1645

The request succeeded. Additional information MAY be returned in the <StatusMessage> and/or<StatusDetail> elements.
urn:oasis:names:tc:SAML:2.0:status:Requester
The request could not be performed due to an error on the part of the requester.
urn:oasis:names:tc:SAML:2.0:status:Responder
The request could not be performed due to an error on the part of the SAML responder or SAML
authority.
urn:oasis:names:tc:SAML:2.0:status:VersionMismatch
The SAML responder could not process the request because the version of the request message wasincorrect.

1646
1647
1648

The following second-level status codes are referenced at various places in this specification. Additional
second-level status codes MAY be defined in future versions of the SAML specification. System entities
are free to define more specific status codes by defining appropriate URI references.

1649

urn:oasis:names:tc:SAML:2.0:status:AuthnFailed

1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665

79
80

The responding provider was unable to successfully authenticate the principal.
urn:oasis:names:tc:SAML:2.0:status:InvalidAttrNameOrValue
Unexpected or invalid content was encountered within a <saml:Attribute> or<saml:AttributeValue> element.
urn:oasis:names:tc:SAML:2.0:status:InvalidNameIDPolicy
The responding provider cannot or will not support the requested name identifier policy.
urn:oasis:names:tc:SAML:2.0:status:NoAuthnContext
The specified authentication context requirements cannot be met by the responder.
urn:oasis:names:tc:SAML:2.0:status:NoAvailableIDP
Used by an intermediary to indicate that none of the supported identity provider <Loc> elements in an<IDPList> can be resolved or that none of the supported identity providers are available.
urn:oasis:names:tc:SAML:2.0:status:NoPassive
Indicates the responding provider cannot authenticate the principal passively, as has been requested.
urn:oasis:names:tc:SAML:2.0:status:NoSupportedIDP
Used by an intermediary to indicate that none of the identity providers in an <IDPList> aresupported by the intermediary.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 40 of 86

1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676

urn:oasis:names:tc:SAML:2.0:status:PartialLogout
Used by a session authority to indicate to a session participant that it was not able to propagate logout
to all other session participants.
urn:oasis:names:tc:SAML:2.0:status:ProxyCountExceeded
Indicates that a responding provider cannot authenticate the principal directly and is not permitted toproxy the request further.
urn:oasis:names:tc:SAML:2.0:status:RequestDenied
The SAML responder or SAML authority is able to process the request but has chosen not to respond.
This status code MAY be used when there is concern about the security context of the request
message or the sequence of request messages received from a particular requester.
urn:oasis:names:tc:SAML:2.0:status:RequestUnsupported

1677

The SAML responder or SAML authority does not support the request.

1678

urn:oasis:names:tc:SAML:2.0:status:RequestVersionDeprecated

1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695

The SAML responder cannot process any requests with the protocol version specified in the request.
urn:oasis:names:tc:SAML:2.0:status:RequestVersionTooHigh
The SAML responder cannot process the request because the protocol version specified in therequest message is a major upgrade from the highest protocol version supported by the responder.
urn:oasis:names:tc:SAML:2.0:status:RequestVersionTooLow
The SAML responder cannot process the request because the protocol version specified in therequest message is too low.
urn:oasis:names:tc:SAML:2.0:status:ResourceNotRecognized
The resource value provided in the request message is invalid or unrecognized.
urn:oasis:names:tc:SAML:2.0:status:TooManyResponses
The response message would contain more elements than the SAML responder is able to return.
urn:oasis:names:tc:SAML:2.0:status:UnknownAttrProfile
An entity that has no knowledge of a particular attribute profile has been presented with an attributedrawn from that profile.
urn:oasis:names:tc:SAML:2.0:status:UnknownPrincipal
The responding provider does not recognize the principal specified or implied by the request.
urn:oasis:names:tc:SAML:2.0:status:UnsupportedBinding

1696
1697

The SAML responder cannot properly fulfill the request using the protocol binding specified in therequest.

1698
1699

The following schema fragment defines the <StatusCode> element and its StatusCodeType complex
type:

1700
1701
1702
1703
1704
1705
1706

81
82

<element name="StatusCode" type="samlp:StatusCodeType"/><complexType name="StatusCodeType"><sequence><element ref="samlp:StatusCode" minOccurs="0"/></sequence><attribute name="Value" type="anyURI" use="required"/></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 41 of 86

1707

3.2.2.3 Element <StatusMessage>1708

The <StatusMessage> element specifies a message that MAY be returned to an operator:

1709

The following schema fragment defines the <StatusMessage> element:1710<element name="StatusMessage" type="string"/>1711

3.2.2.4 Element <StatusDetail>

1712
1713
1714

The <StatusDetail> element MAY be used to specify additional information concerning the status of
the request. The additional information consists of zero or more elements from any namespace, with norequirement for a schema to be present or for schema validation of the <StatusDetail> contents.

1715
1716

The following schema fragment defines the <StatusDetail> element and its StatusDetailTypecomplex type:

1717
1718
1719
1720
1721
1722
1723

<element name="StatusDetail" type="samlp:StatusDetailType"/><complexType name="StatusDetailType"><sequence><any namespace="##any" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/></sequence></complexType>1724

3.3 Assertion Query and Request Protocol

1725
1726

This section defines messages and processing rules for requesting existing assertions by reference orquerying for assertions by subject and statement type.

1727

3.3.1 Element <AssertionIDRequest>

1728
1729
1730
1731

If the requester knows the unique identifier of one or more assertions, the <AssertionIDRequest>
message element can be used to request that they be returned in a <Response> message. The<saml:AssertionIDRef> element is used to specify each assertion to return. See Section 2.3.1 formore information on this element.

1732

The following schema fragment defines the <AssertionIDRequest> element:

1733
1734
1735
1736
1737
1738
1739
1740
1741
1742

<element name="AssertionIDRequest" type="samlp:AssertionIDRequestType"/><complexType name="AssertionIDRequestType"><complexContent><extension base="samlp:RequestAbstractType"><sequence><element ref="saml:AssertionIDRef" maxOccurs="unbounded"/></sequence></extension></complexContent></complexType>1743

3.3.2 Queries

1744

The following sections define the SAML query request messages.

1745

3.3.2.1 Element <SubjectQuery>

1746
1747

The <SubjectQuery> message element is an extension point that allows new SAML queries to be
defined that specify a single SAML subject. Its SubjectQueryAbstractType complex type is abstract and83
84

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 42 of 86

1748
1749

is thus usable only as the base of a derived type. SubjectQueryAbstractType adds the<saml:Subject> element (defined in Section 2.4) to RequestAbstractType.

1750
1751

The following schema fragment defines the <SubjectQuery> element and its
SubjectQueryAbstractType complex type:

1752
1753
1754
1755
1756
1757
1758
1759
1760
1761

<element name="SubjectQuery" type="samlp:SubjectQueryAbstractType"/><complexType name="SubjectQueryAbstractType" abstract="true"><complexContent><extension base="samlp:RequestAbstractType"><sequence><element ref="saml:Subject"/></sequence></extension></complexContent></complexType>1762

3.3.2.2 Element <AuthnQuery>

1763
1764
1765

The <AuthnQuery> message element is used to make the query “What assertions containing
authentication statements are available for this subject?” A successful <Response> will contain one ormore assertions containing authentication statements.

1766
1767
1768

The <AuthnQuery> message MUST NOT be used as a request for a new authentication using
credentials provided in the request. <AuthnQuery> is a request for statements about authentication actsthat have occurred in a previous interaction between the indicated subject and the authentication authority.

1769
1770

This element is of type AuthnQueryType, which extends SubjectQueryAbstractType with the addition of
the following element and attribute:

1771

SessionIndex [Optional]

1772
1773
1774
1775

If present, specifies a filter for possible responses. Such a query asks the question “What assertions
containing authentication statements do you have for this subject within the context of the supplied
session information?”<RequestedAuthnContext> [Optional]

1776
1777
1778

If present, specifies a filter for possible responses. Such a query asks the question "What assertions
containing authentication statements do you have for this subject that satisfy the authentication
context requirements in this element?"

1779
1780
1781
1782

In response to an authentication query, a SAML authority returns assertions with authentication
statements as follows:• Rules given in Section 3.3.4 for matching against the <Subject> element of the query identify theassertions that may be returned.

1783
1784
1785
1786

• If the SessionIndex attribute is present in the query, at least one <AuthnStatement> element in
the set of returned assertions MUST contain a SessionIndex attribute that matches theSessionIndex attribute in the query. It is OPTIONAL for the complete set of all such matchingassertions to be returned in the response.

1787
1788
1789
1790

• If the <RequestedAuthnContext> element is present in the query, at least one<AuthnStatement> element in the set of returned assertions MUST contain an<AuthnContext> element that satisfies the element in the query (see Section 3.3.2.2.1). It is
OPTIONAL for the complete set of all such matching assertions to be returned in the response.

1791
1792

The following schema fragment defines the <AuthnQuery> element and its AuthnQueryType complex
type:

1793

85
86

<element name="AuthnQuery" type="samlp:AuthnQueryType"/>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 43 of 86

1794
1795
1796
1797
1798
1799
1800
1801
1802
1803

<complexType name="AuthnQueryType"><complexContent><extension base="samlp:SubjectQueryAbstractType"><sequence><element ref="samlp:RequestedAuthnContext" minOccurs="0"/></sequence><attribute name="SessionIndex" type="string" use="optional"/></extension></complexContent></complexType>1804

3.3.2.2.1 Element <RequestedAuthnContext>

1805
1806
1807

The <RequestedAuthnContext> element specifies the authentication context requirements ofauthentication statements returned in response to a request or query. Its RequestedAuthnContextTypecomplex type defines the following elements and attributes:

1808<saml:AuthnContextClassRef> or <saml:AuthnContextDeclRef> [One or More]

1809
1810
1811
1812
1813
1814

Specifies one or more URI references identifying authentication context classes or declarations.
These elements are defined in Section 2.7.2.2. For more information about authentication context
classes, see [SAMLAuthnCxt].
Comparison [Optional]
Specifies the comparison method used to evaluate the requested context classes or statements, oneof "exact", "minimum", "maximum", or "better". The default is "exact".

1815
1816
1817
1818
1819

Either a set of class references or a set of declaration references can be used. The set of suppliedreferences MUST be evaluated as an ordered set, where the first element is the most preferredauthentication context class or declaration. If none of the specified classes or declarations can be satisfied
in accordance with the rules below, then the responder MUST return a <Response> message with asecond-level <StatusCode> of urn:oasis:names:tc:SAML:2.0:status:NoAuthnContext.

1820
1821

If Comparison is set to "exact" or omitted, then the resulting authentication context in the authentication
statement MUST be the exact match of at least one of the authentication contexts specified.

1822
1823
1824

If Comparison is set to "minimum", then the resulting authentication context in the authentication
statement MUST be at least as strong (as deemed by the responder) as one of the authentication
contexts specified.

1825
1826
1827

If Comparison is set to "better", then the resulting authentication context in the authentication
statement MUST be stronger (as deemed by the responder) than any one of the authentication contexts
specified.

1828
1829
1830

If Comparison is set to "maximum", then the resulting authentication context in the authentication
statement MUST be as strong as possible (as deemed by the responder) without exceeding the strengthof at least one of the authentication contexts specified.

1831
1832

The following schema fragment defines the <RequestedAuthnContext> element and its
RequestedAuthnContextType complex type:

1833
1834
1835
1836
1837
1838
1839
1840
1841
1842

87
88

<element name="RequestedAuthnContext" type="samlp:RequestedAuthnContextType"/><complexType name="RequestedAuthnContextType"><choice><element ref="saml:AuthnContextClassRef" maxOccurs="unbounded"/><element ref="saml:AuthnContextDeclRef" maxOccurs="unbounded"/></choice><attribute name="Comparison" type="samlp:AuthnContextComparisonType"use="optional"/></complexType><simpleType name="AuthnContextComparisonType">saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 44 of 86

1843
1844
1845
1846
1847
1848
1849

<restriction base="string"><enumeration value="exact"/><enumeration value="minimum"/><enumeration value="maximum"/><enumeration value="better"/></restriction></simpleType>1850

3.3.2.3 Element <AttributeQuery>

1851
1852
1853
1854

The <AttributeQuery> element is used to make the query “Return the requested attributes for thissubject.” A successful response will be in the form of assertions containing attribute statements, to theextent allowed by policy. This element is of type AttributeQueryType, which extends
SubjectQueryAbstractType with the addition of the following element:

1855<saml:Attribute> [Any Number]

1856
1857
1858
1859
1860
1861
1862

Each <saml:Attribute> element specifies an attribute whose value(s) are to be returned. If noattributes are specified, it indicates that all attributes allowed by policy are requested. If a given<saml:Attribute> element contains one or more <saml:AttributeValue> elements, then ifthat attribute is returned in the response, it MUST NOT contain any values that are not equal to thevalues specified in the query. In the absence of equality rules specified by particular profiles or
attributes, equality is defined as an identical XML representation of the value. For more information on<saml:Attribute>, see Section 2.7.3.1.

1863
1864

A single query MUST NOT contain two <saml:Attribute> elements with the same Name and
NameFormat values (that is, a given attribute MUST be named only once in a query).

1865

In response to an attribute query, a SAML authority returns assertions with attribute statements as follows:

1866
1867

• Rules given in Section 3.3.4 for matching against the <Subject> element of the query identify theassertions that may be returned.

1868
1869

• If any <Attribute> elements are present in the query, they constrain/filter the attributes andoptionally the values returned, as noted above.

1870
1871

• The attributes and values returned MAY also be constrained by application-specific policy
considerations.

1872
1873
1874

The second-level status codes urn:oasis:names:tc:SAML:2.0:status:UnknownAttrProfile
and urn:oasis:names:tc:SAML:2.0:status:InvalidAttrNameOrValue MAY be used toindicate problems with the interpretation of attribute or value information in a query.

1875
1876

The following schema fragment defines the <AttributeQuery> element and its AttributeQueryTypecomplex type:

1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887

89
90

<element name="AttributeQuery" type="samlp:AttributeQueryType"/><complexType name="AttributeQueryType"><complexContent><extension base="samlp:SubjectQueryAbstractType"><sequence><element ref="saml:Attribute" minOccurs="0"
maxOccurs="unbounded"/></sequence></extension></complexContent></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 45 of 86

1888

3.3.2.4 Element <AuthzDecisionQuery>

1889
1890
1891

The <AuthzDecisionQuery> element is used to make the query “Should these actions on this resource
be allowed for this subject, given this evidence?” A successful response will be in the form of assertions
containing authorization decision statements.

1892
1893
1894
1895

Note: The <AuthzDecisionQuery> feature has been frozen as of SAML V2.0, with nofuture enhancements planned. Users who require additional functionality may want toconsider the eXtensible Access Control Markup Language [XACML], which offers
enhanced authorization decision features.

1896
1897

This element is of type AuthzDecisionQueryType, which extends SubjectQueryAbstractType with theaddition of the following elements and attribute:

1898

Resource [Required]

1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923

A URI reference indicating the resource for which authorization is requested.
<saml:Action> [One or More]
The actions for which authorization is requested. For more information on this element, see Section
2.7.4.2.
<saml:Evidence> [Optional]
A set of assertions that the SAML authority MAY rely on in making its authorization decision. For more
information on this element, see Section 2.7.4.3.
In response to an authorization decision query, a SAML authority returns assertions with authorization
decision statements as follows:• Rules given in Section 3.3.4 for matching against the <Subject> element of the query identify theassertions that may be returned.
The following schema fragment defines the <AuthzDecisionQuery> element and its
AuthzDecisionQueryType complex type:<element name="AuthzDecisionQuery" type="samlp:AuthzDecisionQueryType"/><complexType name="AuthzDecisionQueryType"><complexContent><extension base="samlp:SubjectQueryAbstractType"><sequence><element ref="saml:Action" maxOccurs="unbounded"/><element ref="saml:Evidence" minOccurs="0"/></sequence><attribute name="Resource" type="anyURI" use="required"/></extension></complexContent></complexType>

1924

3.3.3 Element <Response>

1925
1926
1927

The <Response> message element is used when a response consists of a list of zero or more assertions
that satisfy the request. It has the complex type ResponseType, which extends StatusResponseTypeand adds the following elements:

1928<saml:Assertion> or <saml:EncryptedAssertion> [Any Number]

1929
1930

Specifies an assertion by value, or optionally an encrypted assertion by value. See Section 2.3.3 formore information on these elements.

1931

The following schema fragment defines the <Response> element and its ResponseType complex type:91
92

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 46 of 86

1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942

<element name="Response" type="samlp:ResponseType"/><complexType name="ResponseType"><complexContent><extension base="samlp:StatusResponseType"><choice minOccurs="0" maxOccurs="unbounded"><element ref="saml:Assertion"/><element ref="saml:EncryptedAssertion"/></choice></extension></complexContent></complexType>1943

3.3.4 Processing Rules

1944
1945
1946

In response to a SAML-defined query message, every assertion returned by a SAML authority MUST
contain a <saml:Subject> element that strongly matches the <saml:Subject> element found in thequery.

1947
1948

A <saml:Subject> element S1 strongly matches S2 if and only if the following two conditions both
apply:

1949
1950
1951
1952
1953

• If S2 includes an identifier element (<BaseID>, <NameID>, or <EncryptedID>), then S1 MUST
include an identical identifier element, but the element MAY be encrypted (or not) in either S1 or S2.
In other words, the decrypted form of the identifier MUST be identical in S1 and S2. "Identical"
means that the identifier element's content and attribute values MUST be the same. An encrypted
identifier will be identical to the original according to this definition, once decrypted.

1954
1955
1956

• If S2 includes one or more <saml:SubjectConfirmation> elements, then S1 MUST include atleast one <saml:SubjectConfirmation> element such that S1 can be confirmed in the manner
described by at least one <saml:SubjectConfirmation> element in S2.

1957
1958
1959
1960
1961

As an example of what is and is not permitted, S1 could contain a <saml:NameID> with a particular
Format value, and S2 could contain a <saml:EncryptedID> element that is the result of encrypting
S1's <saml:NameID> element. However, S1 and S2 cannot contain a <saml:NameID> element withdifferent Format values and element content, even if the two identifiers are considered to refer to thesame principal.

1962
1963
1964
1965

If the SAML authority cannot provide an assertion with any statements satisfying the constraints
expressed by a query or assertion reference, the <Response> element MUST NOT contain an<Assertion> element and MUST include a <StatusCode> element with the value
urn:oasis:names:tc:SAML:2.0:status:Success.

1966
1967

All other processing rules associated with the underlying request and response messages MUST beobserved.

1968

3.4 Authentication Request Protocol

1969
1970
1971
1972
1973
1974

When a principal (or an agent acting on the principal's behalf) wishes to obtain assertions containing
authentication statements to establish a security context at one or more relying parties, it can use theauthentication request protocol to send an <AuthnRequest> message element to a SAML authority andrequest that it return a <Response> message containing one or more such assertions. Such assertions
MAY contain additional statements of any type, but at least one assertion MUST contain at least one
authentication statement. A SAML authority that supports this protocol is also termed an identity provider.

1975
1976
1977
1978

Apart from this requirement, the specific contents of the returned assertions depend on the profile orcontext of use. Also, the exact means by which the principal or agent authenticates to the identity provider
is not specified, though the means of authentication might impact the content of the response. Other
issues related to the validation of authentication credentials by the identity provider or any communication

93
94

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 47 of 86

1979
1980

between the identity provider and any other entities involved in the authentication process are also out of
scope of this protocol.

1981
1982

The descriptions and processing rules in the following sections reference the following actors, many ofwhom might be the same entity in a particular profile of use:

1983

Requester

1984
1985
1986
1987
1988
1989
1990
1991

The entity who creates the authentication request and to whom the response is to be returned.
Presenter
The entity who presents the request to the identity provider and either authenticates itself during
the transmission of the message, or relies on an existing security context to establish its identity. If
not the requester, the presenter acts as an intermediary between the requester and the
responding identity provider.
Requested Subject
The entity about whom one or more assertions are being requested.

1993
1994

Attesting Entity
The entity or entities expected to be able to satisfy one of the <SubjectConfirmation>
elements of the resulting assertion(s).

1995

Relying Party

1992

1996
1997

The entity or entities expected to consume the assertion(s) to accomplish a purpose defined by
the profile or context of use, generally to establish a security context.

1998
1999
2000

Identity Provider
The entity to whom the presenter gives the request and from whom the presenter receives the
response.

2001

3.4.1 Element <AuthnRequest>

2002
2003
2004
2005
2006
2007
2008

To request that an identity provider issue an assertion with an authentication statement, a presenter
authenticates to that identity provider (or relies on an existing security context) and sends it an<AuthnRequest> message that describes the properties that the resulting assertion needs to have tosatisfy its purpose. Among these properties may be information that relates to the content of the assertion
and/or information that relates to how the resulting <Response> message should be delivered to therequester. The process of authentication of the presenter may take place before, during, or after the initialdelivery of the <AuthnRequest> message.

2009
2010
2011

The requester might not be the same as the presenter of the request if, for example, the requester is arelying party that intends to use the resulting assertion to authenticate or authorize the requested subject
so that the relying party can decide whether to provide a service.

2012
2013

The <AuthnRequest> message SHOULD be signed or otherwise authenticated and integrity protectedby the protocol binding used to deliver the message.

2014
2015
2016

This message has the complex type AuthnRequestType, which extends RequestAbstractType andadds the following elements and attributes, all of which are optional in general, but may be required by
specific profiles:

2017<saml:Subject> [Optional]

2018
2019
2020

95
96

Specifies the requested subject of the resulting assertion(s). This may include one or more<saml:SubjectConfirmation> elements to indicate how and/or by whom the resulting assertions
can be confirmed. For more information on this element, see Section 2.4.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 48 of 86

2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067

97
98

If entirely omitted or if no identifier is included, the presenter of the message is presumed to be therequested subject. If no <saml:SubjectConfirmation> elements are included, then the presenteris presumed to be the only attesting entity required and the method is implied by the profile of use
and/or the policies of the identity provider.
<NameIDPolicy> [Optional]
Specifies constraints on the name identifier to be used to represent the requested subject. If omitted,
then any type of identifier supported by the identity provider for the requested subject can be used,
constrained by any relevant deployment-specific policies, with respect to privacy, for example.
<saml:Conditions> [Optional]
Specifies the SAML conditions the requester expects to limit the validity and/or use of the resulting
assertion(s). The responder MAY modify or supplement this set as it deems necessary. The
information in this element is used as input to the process of constructing the assertion, rather than as
conditions on the use of the request itself. (For more information on this element, see Section 2.5.)<RequestedAuthnContext> [Optional]
Specifies the requirements, if any, that the requester places on the authentication context that applies
to the responding provider's authentication of the presenter. See Section 3.3.2.2.1 for processing rules
regarding this element.
<Scoping> [Optional]
Specifies a set of identity providers trusted by the requester to authenticate the presenter, as well as
limitations and context related to proxying of the <AuthnRequest> message to subsequent identity
providers by the responder.
ForceAuthn [Optional]
A Boolean value. If "true", the identity provider MUST authenticate the presenter directly rather thanrely on a previous security context. If a value is not provided, the default is "false". However, if both
ForceAuthn and IsPassive are "true", the identity provider MUST NOT freshly authenticate thepresenter unless the constraints of IsPassive can be met.
IsPassive [Optional]
A Boolean value. If "true", the identity provider and the user agent itself MUST NOT visibly take controlof the user interface from the requester and interact with the presenter in a noticeable fashion. If avalue is not provided, the default is "false".
AssertionConsumerServiceIndex [Optional]
Indirectly identifies the location to which the <Response> message should be returned to therequester. It applies only to profiles in which the requester is different from the presenter, such as the
Web Browser SSO profile in [SAMLProf]. The identity provider MUST have a trusted means to map
the index value in the attribute to a location associated with the requester. [SAMLMeta] provides one
possible mechanism. If omitted, then the identity provider MUST return the <Response> message tothe default location associated with the requester for the profile of use. If the index specified is invalid,then the identity provider MAY return an error <Response> or it MAY use the default location. This
attribute is mutually exclusive with the AssertionConsumerServiceURL and ProtocolBinding
attributes.
AssertionConsumerServiceURL [Optional]
Specifies by value the location to which the <Response> message MUST be returned to therequester. The responder MUST ensure by some means that the value specified is in fact associatedwith the requester. [SAMLMeta] provides one possible mechanism; signing the enclosing<AuthnRequest> message is another. This attribute is mutually exclusive with theAssertionConsumerServiceIndex attribute and is typically accompanied by theProtocolBinding attribute.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 49 of 86

2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082

ProtocolBinding [Optional]
A URI reference that identifies a SAML protocol binding to be used when returning the <Response>
message. See [SAMLBind] for more information about protocol bindings and URI references definedfor them. This attribute is mutually exclusive with the AssertionConsumerServiceIndex attributeand is typically accompanied by the AssertionConsumerServiceURL attribute.
AttributeConsumingServiceIndex [Optional]
Indirectly identifies information associated with the requester describing the SAML attributes therequester desires or requires to be supplied by the identity provider in the <Response> message. The
identity provider MUST have a trusted means to map the index value in the attribute to information
associated with the requester. [SAMLMeta] provides one possible mechanism. The identity provider
MAY use this information to populate one or more <saml:AttributeStatement> elements in theassertion(s) it returns.
ProviderName [Optional]
Specifies the human-readable name of the requester for use by the presenter's user agent or theidentity provider.

2083

See Section 3.4.1.4 for general processing rules regarding this message.

2084
2085

The following schema fragment defines the <AuthnRequest> element and its AuthnRequestTypecomplex type:

2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109

<element name="AuthnRequest" type="samlp:AuthnRequestType"/><complexType name="AuthnRequestType"><complexContent><extension base="samlp:RequestAbstractType"><sequence><element ref="saml:Subject" minOccurs="0"/><element ref="samlp:NameIDPolicy" minOccurs="0"/><element ref="saml:Conditions" minOccurs="0"/><element ref="samlp:RequestedAuthnContext" minOccurs="0"/><element ref="samlp:Scoping" minOccurs="0"/></sequence><attribute name="ForceAuthn" type="boolean" use="optional"/><attribute name="IsPassive" type="boolean" use="optional"/><attribute name="ProtocolBinding" type="anyURI" use="optional"/><attribute name="AssertionConsumerServiceIndex" type="unsignedShort"use="optional"/><attribute name="AssertionConsumerServiceURL" type="anyURI"
use="optional"/><attribute name="AttributeConsumingServiceIndex"
type="unsignedShort" use="optional"/><attribute name="ProviderName" type="string" use="optional"/></extension></complexContent></complexType>

2110

3.4.1.1 Element <NameIDPolicy>

2111
2112

The <NameIDPolicy> element tailors the name identifier in the subjects of assertions resulting from an<AuthnRequest>. Its NameIDPolicyType complex type defines the following attributes:

2113

Format [Optional]

2114
2115
2116
2117

99
100

Specifies the URI reference corresponding to a name identifier format defined in this or anotherspecification (see Section 8.3 for examples). The additional value of
urn:oasis:names:tc:SAML:2.0:nameid-format:encrypted is defined specifically for use
within this attribute to indicate a request that the resulting identifier be encrypted.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 50 of 86

2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129

SPNameQualifier [Optional]
Optionally specifies that the assertion subject's identifier be returned (or created) in the namespace ofa service provider other than the requester, or in the namespace of an affiliation group of service
providers. See for example the definition of urn:oasis:names:tc:SAML:2.0:nameidformat:persistent in Section 8.3.7.
AllowCreate [Optional]
A Boolean value used to indicate whether the identity provider is allowed, in the course of fulfilling therequest, to create a new identifier to represent the principal. Defaults to "false". When "false", therequester constrains the identity provider to only issue an assertion to it if an acceptable identifier forthe principal has already been established. Note that this does not prevent the identity provider fromcreating such identifiers outside the context of this specific request (for example, in advance for alarge number of principals).

2130
2131
2132

When this element is used, if the content is not understood by or acceptable to the identity provider, then a<Response> message element MUST be returned with an error <Status>, and MAY contain a secondlevel <StatusCode> of urn:oasis:names:tc:SAML:2.0:status:InvalidNameIDPolicy.

2133
2134
2135

If the Format value is omitted or set to urn:oasis:names:tc:SAML:2.0:nameidformat:unspecified, then the identity provider is free to return any kind of identifier, subject to any
additional constraints due to the content of this element or the policies of the identity provider or principal.

2136
2137
2138
2139

The special Format value urn:oasis:names:tc:SAML:2.0:nameid-format:encrypted indicatesthat the resulting assertion(s) MUST contain <EncryptedID> elements instead of plaintext. The
underlying name identifier's unencrypted form can be of any type supported by the identity provider for therequested subject.

2140
2141
2142

Regardless of the Format in the <NameIDPolicy>, the identity provider MAY return an<EncryptedID> in the resulting assertion subject if the policies in effect at the identity provider (possibly
specific to the service provider) require that an encrypted identifier be used.

2143
2144
2145
2146
2147

Note that if the requester wishes to permit the identity provider to establish a new identifier for the principal
if none exists, it MUST include this element with the AllowCreate attribute set to "true". Otherwise,
only a principal for whom the identity provider has previously established an identifier usable by therequester can be authenticated successfully. This is primarily useful in conjunction with theurn:oasis:names:tc:SAML:2.0:nameid-format:persistent Format value (see Section 8.3.7).

2148
2149

The following schema fragment defines the <NameIDPolicy> element and its NameIDPolicyTypecomplex type:

2150
2151
2152
2153
2154
2155

<element name="NameIDPolicy" type="samlp:NameIDPolicyType"/><complexType name="NameIDPolicyType"><attribute name="Format" type="anyURI" use="optional"/><attribute name="SPNameQualifier" type="string" use="optional"/><attribute name="AllowCreate" type="boolean" use="optional"/></complexType>2156

3.4.1.2 Element <Scoping>

2157
2158
2159
2160

The <Scoping> element specifies the identity providers trusted by the requester to authenticate thepresenter, as well as limitations and context related to proxying of the <AuthnRequest> message tosubsequent identity providers by the responder. Its ScopingType complex type defines the following
elements and attribute:

2161

ProxyCount [Optional]

2162
2163
2164

101
102

Specifies the number of proxying indirections permissible between the identity provider that receives
this <AuthnRequest> and the identity provider who ultimately authenticates the principal. A count ofzero permits no proxying, while omitting this attribute expresses no such restriction.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 51 of 86

2165
2166
2167
2168

<IDPList> [Optional]
An advisory list of identity providers and associated information that the requester deems acceptableto respond to the request.
<RequesterID> [Zero or More]

2169
2170
2171

Identifies the set of requesting entities on whose behalf the requester is acting. Used to communicate
the chain of requesters when proxying occurs, as described in Section 3.4.1.5. See Section 8.3.6 for a
description of entity identifiers.

2172
2173
2174
2175
2176

In profiles specifying an active intermediary, the intermediary MAY examine the list and return a<Response> message with an error <Status> and a second-level <StatusCode> of
urn:oasis:names:tc:SAML:2.0:status:NoAvailableIDP or
urn:oasis:names:tc:SAML:2.0:status:NoSupportedIDP if it cannot contact or does not support
any of the specified identity providers.

2177

The following schema fragment defines the <Scoping> element and its ScopingType complex type:

2178
2179
2180
2181
2182
2183
2184
2185
2186

<element name="Scoping" type="samlp:ScopingType"/><complexType name="ScopingType"><sequence><element ref="samlp:IDPList" minOccurs="0"/><element ref="samlp:RequesterID" minOccurs="0" maxOccurs="unbounded"/></sequence><attribute name="ProxyCount" type="nonNegativeInteger" use="optional"/></complexType><element name="RequesterID" type="anyURI"/>

2187

3.4.1.3 Element <IDPList>

2188
2189

The <IDPList> element specifies the identity providers trusted by the requester to authenticate thepresenter. Its IDPListType complex type defines the following elements:

2190<IDPEntry> [One or More]

2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205

Information about a single identity provider.
<GetComplete> [Optional]
If the <IDPList> is not complete, using this element specifies a URI reference that can be used toretrieve the complete list. Retrieving the resource associated with the URI MUST result in an XML
instance whose root element is an <IDPList> that does not itself contain a <GetComplete>element.
The following schema fragment defines the <IDPList> element and its IDPListType complex type:<element name="IDPList" type="samlp:IDPListType"/><complexType name="IDPListType"><sequence><element ref="samlp:IDPEntry" maxOccurs="unbounded"/><element ref="samlp:GetComplete" minOccurs="0"/></sequence></complexType><element name="GetComplete" type="anyURI"/>

2206

3.4.1.3.1 Element <IDPEntry>

2207
2208

The <IDPEntry> element specifies a single identity provider trusted by the requester to authenticate thepresenter. Its IDPEntryType complex type defines the following attributes:

2209

ProviderID [Required]

2210

103
104

The unique identifier of the identity provider. See Section 8.3.6 for a description of such identifiers.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 52 of 86

2211
2212
2213

Name [Optional]
A human-readable name for the identity provider.
Loc [Optional]

2214
2215

A URI reference representing the location of a profile-specific endpoint supporting the authentication
request protocol. The binding to be used must be understood from the profile of use.

2216

The following schema fragment defines the <IDPEntry> element and its IDPEntryType complex type:<element name="IDPEntry" type="samlp:IDPEntryType"/><complexType name="IDPEntryType"><attribute name="ProviderID" type="anyURI" use="required"/><attribute name="Name" type="string" use="optional"/><attribute name="Loc" type="anyURI" use="optional"/></complexType>

2217
2218
2219
2220
2221
2222
2223

3.4.1.4 Processing Rules

2224
2225
2226
2227
2228

The <AuthnRequest> and <Response> exchange supports a variety of usage scenarios and istherefore typically profiled for use in a specific context in which this optionality is constrained and specifickinds of input and output are required or prohibited. The following processing rules apply as invariant
behavior across any profile of this protocol exchange. All other processing rules associated with theunderlying request and response messages MUST also be observed.

2229
2230
2231
2232
2233
2234
2235
2236
2237

The responder MUST ultimately reply to an <AuthnRequest> with a <Response> message containing
one or more assertions that meet the specifications defined by the request, or with a <Response>
message containing a <Status> describing the error that occurred. The responder MAY conduct
additional message exchanges with the presenter as needed to initiate or complete the authentication
process, subject to the nature of the protocol binding and the authentication mechanism. As described in
the next section, this includes proxying the request by directing the presenter to another identity provider
by issuing its own <AuthnRequest> message, so that the resulting assertion can be used toauthenticate the presenter to the original responder, in effect using SAML as the authentication
mechanism.

2238
2239
2240
2241
2242
2243

If the responder is unable to authenticate the presenter or does not recognize the requested subject, or if
prevented from providing an assertion by policies in effect at the identity provider (for example theintended subject has prohibited the identity provider from providing assertions to the relying party), then it
MUST return a <Response> with an error <Status>, and MAY return a second-level <StatusCode> of
urn:oasis:names:tc:SAML:2.0:status:AuthnFailed or
urn:oasis:names:tc:SAML:2.0:status:UnknownPrincipal.

2244
2245
2246
2247

If the <saml:Subject> element in the request is present, then the resulting assertions'<saml:Subject> MUST strongly match the request <saml:Subject>, as described in Section 3.3.4,
except that the identifier MAY be in a different format if specified by <NameIDPolicy>. In such a case,the identifier's physical content MAY be different, but it MUST refer to the same principal.

2248
2249

All of the content defined specifically within <AuthnRequest> is optional, although some may be requiredby certain profiles. In the absence of any specific content at all, the following behavior is implied:

2250
2251
2252
2253

•

The assertion(s) returned MUST contain a <saml:Subject> element that represents thepresenter. The identifier type and format are determined by the identity provider. At least one
statement in at least one assertion MUST be a <saml:AuthnStatement> that describes theauthentication performed by the responder or authentication service associated with it.

2254
2255
2256

•

The request presenter should, to the extent possible, be the only attesting entity able to satisfy the<saml:SubjectConfirmation> of the assertion(s). In the case of weaker confirmation
methods, binding-specific or other mechanisms will be used to help satisfy this requirement.

105
106

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 53 of 86

2257
2258
2259

•

The resulting assertion(s) MUST contain a <saml:AudienceRestriction> element
referencing the requester as an acceptable relying party. Other audiences MAY be included as
deemed appropriate by the identity provider.

2260

3.4.1.5 Proxying

2261
2262
2263
2264
2265
2266

If an identity provider that receives an <AuthnRequest> has not yet authenticated the presenter orcannot directly authenticate the presenter, but believes that the presenter has already authenticated toanother identity provider or a non-SAML equivalent, it may respond to the request by issuing a new<AuthnRequest> on its own behalf to be presented to the other identity provider, or a request inwhatever non-SAML format the entity recognizes. The original identity provider is termed the proxying
identity provider.

2267
2268
2269
2270
2271
2272

Upon the successful return of a <Response> (or non-SAML equivalent) to the proxying provider, theenclosed assertion or non-SAML equivalent MAY be used to authenticate the presenter so that theproxying provider can issue an assertion of its own in response to the original <AuthnRequest>,
completing the overall message exchange. Both the proxying and authenticating identity providers MAY
include constraints on proxying activity in the messages and assertions they issue, as described inprevious sections and below.

2273
2274
2275

The requester can influence proxy behavior by including a <Scoping> element where the provider sets a
desired ProxyCount value and/or indicates a list of preferred identity providers which may be proxied byincluding an ordered <IDPList> of preferred providers.

2276
2277

An identity provider can control secondary use of its assertions by proxying identity providers using a<ProxyRestriction> element in the assertions it issues.

2278

3.4.1.5.1 Proxying Processing Rules

2279
2280
2281

An identity provider MAY proxy an <AuthnRequest> if the <ProxyCount> attribute is omitted or isgreater than zero. Whether it chooses to proxy or not is a matter of local policy. An identity provider MAY
choose to proxy for a provider specified in the <IDPList>, if provided, but is not required to do so.

2282
2283
2284
2285

An identity provider MUST NOT proxy a request where <ProxyCount> is set to zero. The identity
provider MUST return an error <Status> containing a second-level <StatusCode> value of
urn:oasis:names:tc:SAML:2.0:status:ProxyCountExceeded, unless it can directly
authenticate the presenter.

2286
2287
2288
2289

If it chooses to proxy to a SAML identity provider, when creating the new <AuthnRequest>, the proxying
identity provider MUST include equivalent or stricter forms of all the information included in the original
request (such as authentication context policy). Note, however, that the proxying provider is free to specify
whatever <NameIDPolicy> it wishes to maximize the chances of a successful response.

2290
2291
2292

If the authenticating identity provider is not a SAML identity provider, then the proxying provider MUST
have some other way to ensure that the elements governing user agent interaction (<IsPassive>, forexample) will be honored by the authenticating provider.

2293
2294
2295

The new <AuthnRequest> MUST contain a <ProxyCount> attribute with a value of at most one lessthan the original value. If the original request does not contain a <ProxyCount> attribute, then the new
request SHOULD contain a <ProxyCount> attribute.

2296
2297
2298

If an <IDPList> was specified in the original request, the new request MUST also contain an<IDPList>. The proxying identity provider MAY add additional identity providers to the end of the<IDPList>, but MUST NOT remove any from the list.

107
108

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 54 of 86

2299
2300
2301

The authentication request and response are processed in normal fashion, in accordance with the rules
given in this section and the profile of use. Once the presenter has authenticated to the proxying identity
provider (in the case of SAML by delivering a <Response>), the following steps are followed:

2302
2303

•

The proxying identity provider prepares a new assertion on its own behalf by copying in therelevant information from the original assertion or non-SAML equivalent.

2304
2305

•

The new assertion's <saml:Subject> MUST contain an identifier that satisfies the original
requester 's preferences, as defined by its <NameIDPolicy> element.

2306
2307
2308
2309
2310
2311

•

The <saml:AuthnStatement> in the new assertion MUST include a <saml:AuthnContext>
element containing a <saml:AuthenticatingAuthority> element referencing the identity
provider to which the proxying identity provider referred the presenter. If the original assertion
contains <saml:AuthnContext> information that includes one or more<saml:AuthenticatingAuthority> elements, those elements SHOULD be included in the
new assertion, with the new element placed after them.

2312
2313
2314
2315

•

If the authenticating identity provider is not a SAML provider, then the proxying identity provider
MUST generate a unique identifier value for the authenticating provider. This value SHOULD beconsistent over time across different requests. The value MUST not conflict with values used or
generated by other SAML providers.

2316
2317
2318

•

Any other <saml:AuthnContext> information MAY be copied, translated, or omitted inaccordance with the policies of the proxying identity provider, provided that the original
requirements dictated by the requester are met.

2319
2320
2321
2322
2323

If, in the future, the identity provider is asked to authenticate the same presenter for a second requester,and this request is equally or less strict than the original request (as determined by the proxying identity
provider), the identity provider MAY skip the creation of a new <AuthnRequest> to the authenticating
identity provider and immediately issue another assertion (assuming the original assertion or non-SAML
equivalent it received is still valid).

2324

3.5 Artifact Resolution Protocol

2325
2326
2327
2328
2329
2330
2331

The artifact resolution protocol provides a mechanism by which SAML protocol messages can betransported in a SAML binding by reference instead of by value. Both requests and responses can beobtained by reference using this specialized protocol. A message sender, instead of binding a message toa transport protocol, sends a small piece of data called an artifact using the binding. An artifact can take avariety of forms, but must support a means by which the receiver can determine who sent it. If the receiverwishes, it can then use this protocol in conjunction with a different (generally synchronous) SAML binding
protocol to resolve the artifact into the original protocol message.

2332
2333
2334

The most common use for this mechanism is with bindings that cannot easily carry a message because of
size constraints, or to enable a message to be communicated via a secure channel between the SAML
requester and responder, avoiding the need for a signature.

2335
2336
2337
2338
2339

Depending on the characteristics of the underlying message being passed by reference, the artifact
resolution protocol MAY require protections such as mutual authentication, integrity protection,
confidentiality, etc. from the protocol binding used to resolve the artifact. In all cases, the artifact MUST
exhibit a single-use semantic such that once it has been successfully resolved, it can no longer be usedby any party.

2340
2341

Regardless of the protocol message obtained, the result of resolving an artifact MUST be treated exactly
as if the message so obtained had been sent originally in place of the artifact.

109
110

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 55 of 86

2342

3.5.1 Element <ArtifactResolve>

2343
2344
2345
2346

The <ArtifactResolve> message is used to request that a SAML protocol message be returned in an<ArtifactResponse> message by specifying an artifact that represents the SAML protocol message.
The original transmission of the artifact is governed by the specific protocol binding that is being used; see[SAMLBind] for more information on the use of artifacts in bindings.

2347
2348

The <ArtifactResolve> message SHOULD be signed or otherwise authenticated and integrity
protected by the protocol binding used to deliver the message.

2349
2350

This message has the complex type ArtifactResolveType, which extends RequestAbstractType andadds the following element:

2351<Artifact> [Required]

2352
2353

The artifact value that the requester received and now wishes to translate into the protocol message it
represents. See [SAMLBind] for specific artifact format information.

2354
2355

The following schema fragment defines the <ArtifactResolve> element and its ArtifactResolveTypecomplex type:

2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366

<element name="ArtifactResolve" type="samlp:ArtifactResolveType"/><complexType name="ArtifactResolveType"><complexContent><extension base="samlp:RequestAbstractType"><sequence><element ref="samlp:Artifact"/></sequence></extension></complexContent></complexType><element name="Artifact" type="string"/>

2367

3.5.2 Element <ArtifactResponse>

2368
2369
2370
2371

The recipient of an <ArtifactResolve> message MUST respond with an <ArtifactResponse>
message element. This element is of complex type ArtifactResponseType, which extends
StatusResponseType with a single optional wildcard element corresponding to the SAML protocol
message being returned. This wrapped message element can be a request or a response.

2372
2373

The <ArtifactResponse> message SHOULD be signed or otherwise authenticated and integrity
protected by the protocol binding used to deliver the message.

2374
2375

The following schema fragment defines the <ArtifactResponse> element and its
ArtifactResponseType complex type:

2376
2377
2378
2379
2380
2381
2382
2383
2384
2385

<element name="ArtifactResponse" type="samlp:ArtifactResponseType"/><complexType name="ArtifactResponseType"><complexContent><extension base="samlp:StatusResponseType"><sequence><any namespace="##any" processContents="lax" minOccurs="0"/></sequence></extension></complexContent></complexType>

2386

3.5.3 Processing Rules

2387
2388

If the responder recognizes the artifact as valid, then it responds with the associated protocol message inan <ArtifactResponse> message element. Otherwise, it responds with an <ArtifactResponse>

111
112

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 56 of 86

2389
2390
2391
2392

element with no embedded message. In both cases, the <Status> element MUST include a<StatusCode> element with the code value urn:oasis:names:tc:SAML:2.0:status:Success. A
response message with no embedded message inside it is termed an empty response in the remainder ofthis section.

2393
2394

The responder MUST enforce a one-time-use property on the artifact by ensuring that any subsequent
request with the same artifact by any requester results in an empty response as described above.

2395
2396
2397
2398
2399
2400

Some SAML protocol messages, most particularly the <AuthnRequest> message in some profiles, MAY
be intended for consumption by any party that receives it and can respond appropriately. In most othercases, however, a message is intended for a specific entity. In such cases, the artifact when issued MUST
be associated with the intended recipient of the message that the artifact represents. If the artifact issuer
receives an <ArtifactResolve> message from a requester that cannot authenticate itself as theoriginal intended recipient, then the artifact issuer MUST return an empty response.

2401
2402
2403

The artifact issuer SHOULD enforce the shortest practical time limit on the usability of an artifact, suchthat an acceptable window of time (but no more) exists for the artifact receiver to obtain the artifact andreturn it in an <ArtifactResolve> message to the issuer.

2404
2405
2406
2407
2408

Note that the <ArtifactResponse> message's InResponseTo attribute MUST contain the value ofthe corresponding <ArtifactResolve> message's ID attribute, but the embedded protocol message
will contain its own message identifier, and in the case of an embedded response, may contain a different
InResponseTo value that corresponds to the original request message to which the embedded message
is responding.

2409
2410

All other processing rules associated with the underlying request and response messages MUST beobserved.

2411

3.6 Name Identifier Management Protocol

2412
2413
2414
2415

After establishing a name identifier for a principal, an identity provider wishing to change the value and/or
format of the identifier that it will use when referring to the principal, or to indicate that a name identifier will
no longer be used to refer to the principal, informs service providers of the change by sending them a<ManageNameIDRequest> message.

2416
2417
2418

A service provider also uses this message to register or change the SPProvidedID value to be included
when the underlying name identifier is used to communicate with it, or to terminate the use of a nameidentifier between itself and the identity provider.

2419
2420

Note that this protocol is typically not used with "transient" name identifiers, since their value is notintended to be managed on a long term basis.

2421

3.6.1 Element <ManageNameIDRequest>

2422
2423

A provider sends a <ManageNameIDRequest> message to inform the recipient of a changed nameidentifier or to indicate the termination of the use of a name identifier.

2424
2425

The <ManageNameIDRequest> message SHOULD be signed or otherwise authenticated and integrity
protected by the protocol binding used to deliver the message.

2426
2427

This message has the complex type ManageNameIDRequestType, which extends
RequestAbstractType and adds the following elements:

2428<saml:NameID> or <saml:EncryptedID> [Required]

2429
2430
2431

113
114

The name identifier and associated descriptive data (in plaintext or encrypted form) that specify theprincipal as currently recognized by the identity and service providers prior to this request. (For more
information on these elements, see Section 2.2.)

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 57 of 86

2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462

<NewID> or <NewEncryptedID> or <Terminate> [Required]
The new identifier value (in plaintext or encrypted form) to be used when communicating with therequesting provider concerning this principal, or an indication that the use of the old identifier has
been terminated. In the former case, if the requester is the service provider, the new identifier MUST
appear in subsequent <NameID> elements in the SPProvidedID attribute. If the requester is theidentity provider, the new value will appear in subsequent <NameID> elements as the element's
content.
The following schema fragment defines the <ManageNameIDRequest> element and its
ManageNameIDRequestType complex type:<element name="ManageNameIDRequest" type="samlp:ManageNameIDRequestType"/><complexType name="ManageNameIDRequestType"><complexContent><extension base="samlp:RequestAbstractType"><sequence><choice><element ref="saml:NameID"/><element ref="saml:EncryptedID"/></choice><choice><element ref="samlp:NewID"/><element ref="samlp:NewEncryptedID"/><element ref="samlp:Terminate"/></choice></sequence></extension></complexContent></complexType><element name="NewID" type="string"/><element name="NewEncryptedID" type="saml:EncryptedElementType"/><element name="Terminate" type="samlp:TerminateType"/><complexType name="TerminateType"/>2463

3.6.2 Element <ManageNameIDResponse>

2464
2465
2466

The recipient of a <ManageNameIDRequest> message MUST respond with a<ManageNameIDResponse> message, which is of type StatusResponseType with no additional
content.

2467
2468

The <ManageNameIDResponse> message SHOULD be signed or otherwise authenticated and integrity
protected by the protocol binding used to deliver the message.

2469

The following schema fragment defines the <ManageNameIDResponse> element:

2470<element name="ManageNameIDResponse" type="samlp:StatusResponseType"/>2471

3.6.3 Processing Rules

2472
2473
2474

If the request includes a <saml:NameID> (or encrypted version) that the recipient does not recognize,
the responding provider MUST respond with an error <Status> and MAY respond with a second-level<StatusCode> of urn:oasis:names:tc:SAML:2.0:status:UnknownPrincipal.

2475
2476
2477
2478
2479
2480

If the <Terminate> element is included in the request, the requesting provider is indicating that (in thecase of a service provider) it will no longer accept assertions from the identity provider or (in the case of
an identity provider) it will no longer issue assertions to the service provider about the principal. The
receiving provider can perform any maintenance with the knowledge that the relationship represented by
the name identifier has been terminated. It can choose to invalidate the active session(s) of a principal forwhom a relationship has been terminated.

115
116

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 58 of 86

2481
2482
2483

If the service provider requests that its identifier for the principal be changed by including a <NewID> (or<NewEncryptedID>) element, the identity provider MUST include the element's content as the
SPProvidedID when subsequently communicating to the service provider regarding this principal.

2484
2485
2486
2487

If the identity provider requests that its identifier for the principal be changed by including a <NewID> (or<NewEncryptedID>) element, the service provider MUST use the element's content as the<saml:NameID> element content when subsequently communicating with the identity provider regarding
this principal.

2488
2489

Note that neither, either, or both of the original and new identifier MAY be encrypted (using the<EncryptedID> and <NewEncryptedID> elements).

2490
2491
2492

In any case, the <saml:NameID> content in the request and its associated SPProvidedID attribute
MUST contain the most recent name identifier information established between the providers for the
principal.

2493
2494
2495
2496
2497
2498
2499
2500

In the case of an identifier with a Format of urn:oasis:names:tc:SAML:2.0:nameidformat:persistent, the NameQualifier attribute MUST contain the unique identifier of the identity
provider that created the identifier. If the identifier was established between the identity provider and anaffiliation group of which the service provider is a member, then the SPNameQualifier attribute MUST
contain the unique identifier of the affiliation group. Otherwise, it MUST contain the unique identifier of theservice provider. These attributes MAY be omitted if they would otherwise match the value of thecontaining protocol message's <Issuer> element, but this is NOT RECOMMENDED due to theopportunity for confusion.

2501
2502
2503
2504

Changes to these identifiers may take a potentially significant amount of time to propagate through thesystems at both the requester and the responder. Implementations might wish to allow each party toaccept either identifier for some period of time following the successful completion of a name identifierchange. Not doing so could result in the inability of the principal to access resources.

2505
2506

All other processing rules associated with the underlying request and response messages MUST beobserved.

2507

3.7 Single Logout Protocol

2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528

The single logout protocol provides a message exchange protocol by which all sessions provided by aparticular session authority are near-simultaneously terminated. The single logout protocol is used either
when a principal logs out at a session participant or when the principal logs out directly at thesession authority. This protocol may also be used to log out a principal due to a timeout. The reason forthe logout event can be indicated through the Reason attribute.

117
118

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

The principal may have established authenticated sessions with both the session authority and individual
session participants, based on assertions containing authentication statements supplied by the session
authority.
When the principal invokes the single logout process at a session participant, the session participant
MUST send a <LogoutRequest> message to the session authority that provided the assertion
containing the authentication statement related to that session at the session participant.
When either the principal invokes a logout at the session authority, or a session participant sends a logout
request to the session authority specifying that principal, the session authority SHOULD send a<LogoutRequest> message to each session participant to which it provided assertions containing
authentication statements under its current session with the principal, with the exception of the session
participant that sent the <LogoutRequest> message to the session authority. It SHOULD attempt tocontact as many of these participants as it can using this protocol, terminate its own session with theprincipal, and finally return a <LogoutResponse> message to the requesting session participant, if any.

15 March 2005
Page 59 of 86

2529

3.7.1 Element <LogoutRequest>

2530
2531

A session participant or session authority sends a <LogoutRequest> message to indicate that a session
has been terminated.

2532
2533

The <LogoutRequest> message SHOULD be signed or otherwise authenticated and integrity protectedby the protocol binding used to deliver the message.

2534
2535

This message has the complex type LogoutRequestType, which extends RequestAbstractType andadds the following elements and attributes:

2536

NotOnOrAfter [Optional]

2537
2538
2539

The time at which the request expires, after which the recipient may discard the message. The timevalue is encoded in UTC, as described in Section 1.3.3.
Reason [Optional]

2540

An indication of the reason for the logout, in the form of a URI reference.

2541<saml:BaseID> or <saml:NameID> or <saml:EncryptedID> [Required]

2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568

The identifier and associated attributes (in plaintext or encrypted form) that specify the principal as
currently recognized by the identity and service providers prior to this request. (For more informationon this element, see Section 2.2.)<SessionIndex> [Optional]
The identifier that indexes this session at the message recipient.
The following schema fragment defines the <LogoutRequest> element and associated
LogoutRequestType complex type:<element name="LogoutRequest" type="samlp:LogoutRequestType"/><complexType name="LogoutRequestType"><complexContent><extension base="samlp:RequestAbstractType"><sequence><choice><element ref="saml:BaseID"/><element ref="saml:NameID"/><element ref="saml:EncryptedID"/></choice><element ref="samlp:SessionIndex" minOccurs="0"
maxOccurs="unbounded"/></sequence><attribute name="Reason" type="string" use="optional"/><attribute name="NotOnOrAfter" type="dateTime"use="optional"/></extension></complexContent></complexType><element name="SessionIndex" type="string"/>

2569

3.7.2 Element <LogoutResponse>

2570
2571

The recipient of a <LogoutRequest> message MUST respond with a <LogoutResponse> message, oftype StatusResponseType, with no additional content specified.

2572
2573

The <LogoutResponse> message SHOULD be signed or otherwise authenticated and integrity
protected by the protocol binding used to deliver the message.

2574

The following schema fragment defines the <LogoutResponse> element:

119
120

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 60 of 86

<element name="LogoutResponse" type="samlp:StatusResponseType"/>

2575

2576

3.7.3 Processing Rules

2577
2578
2579

The message sender MAY use the Reason attribute to indicate the reason for sending the<LogoutRequest>. The following values are defined by this specification for use by all message
senders; other values MAY be agreed on between participants:

2580

urn:oasis:names:tc:SAML:2.0:logout:user
Specifies that the message is being sent because the principal wishes to terminate the indicatedsession.

2581
2582
2583

urn:oasis:names:tc:SAML:2.0:logout:admin
Specifies that the message is being sent because an administrator wishes to terminate the indicatedsession for that principal.

2584
2585
2586
2587

All other processing rules associated with the underlying request and response messages MUST beobserved.

2588

Additional processing rules are provided in the following sections.

2589

3.7.3.1 Session Participant Rules

2590
2591
2592
2593
2594
2595
2596
2597
2598
2599

When a session participant receives a <LogoutRequest> message, the session participant MUST
authenticate the message. If the sender is the authority that provided an assertion containing anauthentication statement linked to the principal's current session, the session participant MUST invalidate
the principal's session(s) referred to by the <saml:BaseID>, <saml:NameID>, or<saml:EncryptedID> element, and any <SessionIndex> elements supplied in the message. If no<SessionIndex> elements are supplied, then all sessions associated with the principal MUST be
invalidated.
The session participant MUST apply the logout request message to any assertion that meets the following
conditions, even if the assertion arrives after the logout request:

2600
2601

•

The subject of the assertion strongly matches the <saml:BaseID>, <saml:NameID>, or<saml:EncryptedID> element in the <LogoutRequest>, as defined in Section 3.3.4.

2602
2603
2604

•

The SessionIndex attribute of one of the assertion's authentication statements matches one of
the <SessionIndex> elements specified in the logout request, or the logout request contains no<SessionIndex> elements.

2605
2606
2607

•

The assertion would otherwise be valid, based on the time conditions specified in the assertion itself(in particular, the value of any specified NotOnOrAfter attributes in conditions or subject
confirmation data).

2608
2609

•

The logout request has not yet expired (determined by examining the NotOnOrAfter attribute on
the message).

2610
2611
2612
2613
2614
2615
2616

121
122

Note: This rule is intended to prevent a situation in which a session participant receives alogout request targeted at a single, or multiple, assertion(s) (as identified by the<SessionIndex> element(s)) before it receives the actual – and possibly still valid assertion(s) targeted by the logout request. It should honor the logout request until the
logout request itself may be discarded (the NotOnOrAfter value on the request has
been exceeded) or the assertion targeted by the logout request has been received andhas been handled appropriately.

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 61 of 86

2617

3.7.3.2 Session Authority Rules

2618
2619
2620
2621

When a session authority receives a <LogoutRequest> message, the session authority MUST
authenticate the sender. If the sender is a session participant to which the session authority provided an
assertion containing an authentication statement for the current session, then the session authority
SHOULD do the following in the specified order:• Send a <LogoutRequest> message to any session authority on behalf of whom the session
authority proxied the principal's authentication, unless the second authority is the originator of the<LogoutRequest>.

2622
2623
2624
2625
2626
2627

•

Send a <LogoutRequest> message to each session participant for which the session authority
provided assertions in the current session, other than the originator of a current<LogoutRequest>.

2628
2629
2630

•

Terminate the principal's current session as specified by the <saml:BaseID>, <saml:NameID>,or <saml:EncryptedID> element, and any <SessionIndex> elements present in the logout
request message.

2631
2632
2633
2634
2635
2636

If the session authority successfully terminates the principal's session with respect to itself, then it MUST
respond to the original requester, if any, with a <LogoutResponse> message containing a top-levelstatus code of urn:oasis:names:tc:SAML:2.0:status:Success. If it cannot do so, then it MUST
respond with a <LogoutResponse> message containing a top-level status code indicating the error.
Thus, the top-level status indicates the state of the logout operation only with respect to the session
authority itself.

2637
2638
2639
2640

The session authority SHOULD attempt to contact each session participant using any applicable/usable
protocol binding, even if one or more of these attempts fails or cannot be attempted (for example because
the original request takes place using a protocol binding that does not enable the logout to be propagatedto all participants).

2641
2642
2643
2644
2645

In the event that not all session participants successfully respond to these <LogoutRequest> messages(or if not all participants can be contacted), then the session authority MUST include in its<LogoutResponse> message a second-level status code ofurn:oasis:names:tc:SAML:2.0:status:PartialLogout to indicate that not all other session
participants successfully responded with confirmation of the logout.

2646
2647

Note that a session authority MAY initiate a logout for reasons other than having received a<LogoutRequest> from a session participant – these include, but are not limited to:

2648
2649

• If some timeout period was agreed out-of-band with an individual session participant, the session
authority MAY send a <LogoutRequest> to that individual participant alone.

2650• An agreed global timeout period has been exceeded.

2651
2652

• The principal or some other trusted entity has requested logout of the principal directly at the session
authority.

2653• The session authority has determined that the principal's credentials may have been compromised.

2654
2655
2656
2657
2658
2659

When constructing a logout request message, the session authority MUST set the value of the
NotOnOrAfter attribute of the message to a time value, indicating an expiration time for the message,
after which the logout request may be discarded by the recipient. This value SHOULD be set to a timevalue equal to or greater than the value of any NotOnOrAfter attribute specified in the assertion mostrecently issued as part of the targeted session (as indicated by the SessionIndex attribute on the logout
request).

2660
2661

In addition to the values specified in Section 3.6.3 for the Reason attribute, the following values are alsoavailable for use by the session authority only:2662

urn:oasis:names:tc:SAML:2.0:logout:global-timeout

123
124

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 62 of 86

2663
2664
2665
2666
2667

Specifies that the message is being sent because of the global session timeout interval period
being exceeded.
urn:oasis:names:tc:SAML:2.0:logout:sp-timeout
Specifies that the message is being sent because a timeout interval period agreed between aparticipant and the session authority has been exceeded.

2668

3.8 Name Identifier Mapping Protocol

2669
2670
2671

When an entity that shares an identifier for a principal with an identity provider wishes to obtain a nameidentifier for the same principal in a particular format or federation namespace, it can send a request to
the identity provider using this protocol.

2672
2673
2674
2675

For example, a service provider that wishes to communicate with another service provider with whom it
does not share an identifier for the principal can use an identity provider that shares an identifier for the
principal with both service providers to map from its own identifier to a new identifier, generally encrypted,
with which it can communicate with the second service provider.

2676
2677

Regardless of the type of identifier involved, the mapped identifier SHOULD be encrypted into a<saml:EncryptedID> element unless a specific deployment dictates such protection is unnecessary.

2678

3.8.1 Element <NameIDMappingRequest>

2679
2680
2681

To request an alternate name identifier for a principal from an identity provider, a requester sends an<NameIDMappingRequest> message. This message has the complex type
NameIDMappingRequestType, which extends RequestAbstractType and adds the following elements:

2682<saml:BaseID> or <saml:NameID> or <saml:EncryptedID> [Required]

2683
2684
2685
2686

The identifier and associated descriptive data that specify the principal as currently recognized by therequester and the responder. (For more information on this element, see Section 2.2.)<NameIDPolicy> [Required]
The requirements regarding the format and optional name qualifier for the identifier to be returned.

2687
2688

The message SHOULD be signed or otherwise authenticated and integrity protected by the protocol
binding used to deliver the message.

2689
2690

The following schema fragment defines the <NameIDMappingRequest> element and its
NameIDMappingRequestType complex type:

2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705

125
126

<element name="NameIDMappingRequest" type="samlp:NameIDMappingRequestType"/><complexType name="NameIDMappingRequestType"><complexContent><extension base="samlp:RequestAbstractType"><sequence><choice><element ref="saml:BaseID"/><element ref="saml:NameID"/><element ref="saml:EncryptedID"/></choice><element ref="samlp:NameIDPolicy"/></sequence></extension></complexContent></complexType>saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 63 of 86

2706

3.8.2 Element <NameIDMappingResponse>

2707
2708
2709

The recipient of a <NameIDMappingRequest> message MUST respond with a<NameIDMappingResponse> message. This message has the complex type
NameIDMappingResponseType, which extends StatusResponseType and adds the following element:

2710<saml:NameID> or <saml:EncryptedID> [Required]

2711
2712

The identifier and associated attributes that specify the principal in the manner requested, usually inencrypted form. (For more information on this element, see Section 2.2.)

2713
2714

The message SHOULD be signed or otherwise authenticated and integrity protected by the protocol
binding used to deliver the message.

2715
2716

The following schema fragment defines the <NameIDMappingResponse> element and its
NameIDMappingResponseType complex type:

2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727

<element name="NameIDMappingResponse" type="samlp:NameIDMappingResponseType"/><complexType name="NameIDMappingResponseType"><complexContent><extension base="samlp:StatusResponseType"><choice><element ref="saml:NameID"/><element ref="saml:EncryptedID"/></choice></extension></complexContent></complexType>

2728

3.8.3 Processing Rules

2729
2730
2731

If the responder does not recognize the principal identified in the request, it MAY respond with an error<Status> containing a second-level <StatusCode> of
urn:oasis:names:tc:SAML:2.0:status:UnknownPrincipal.

2732
2733
2734

At the responder's discretion, theurn:oasis:names:tc:SAML:2.0:status:InvalidNameIDPolicy status code MAY be returned toindicate an inability or unwillingness to supply an identifier in the requested format or namespace.

2735
2736

All other processing rules associated with the underlying request and response messages MUST beobserved.

127
128

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 64 of 86

2737

4 SAML Versioning

2738
2739
2740
2741

The SAML specification set is versioned in two independent ways. Each is discussed in the following
sections, along with processing rules for detecting and handling version differences. Also included are
guidelines on when and why specific version information is expected to change in future revisions of thespecification.

2742
2743
2744

When version information is expressed as both a Major and Minor version, it is expressed in the form
Major.Minor. The version number MajorB.MinorB is higher than the version number MajorA.MinorA if andonly if:

2745(MajorB > MajorA) OR ( ( MajorB = MajorA ) AND (MinorB > MinorA ))2746

4.1 SAML Specification Set Version

2747
2748
2749
2750
2751
2752

Each release of the SAML specification set will contain a major and minor version designation describing
its relationship to earlier and later versions of the specification set. The version will be expressed in thecontent and filenames of published materials, including the specification set documents and XML schema
documents. There are no normative processing rules surrounding specification set versioning, since itmerely encompasses the collective release of normative specification documents which themselvescontain processing rules.

2753
2754
2755
2756
2757

The overall size and scope of changes to the specification set documents will informally dictate whether aset of changes constitutes a major or minor revision. In general, if the specification set is backwards
compatible with an earlier specification set (that is, valid older syntax, protocols, and semantics remain
valid), then the new version will be a minor revision. Otherwise, the changes will constitute a majorrevision.

2758

4.1.1 Schema Version

2759
2760
2761
2762
2763

As a non-normative documentation mechanism, any XML schema documents published as part of thespecification set will contain a version attribute on the <xs:schema> element whose value is in theform Major.Minor, reflecting the specification set version in which it has been published. Validating
implementations MAY use the attribute as a means of distinguishing which version of a schema is being
used to validate messages, or to support multiple versions of the same logical schema.

2764

4.1.2 SAML Assertion Version

2765
2766
2767
2768

The SAML <Assertion> element contains an attribute for expressing the major and minor version of theassertion in a string of the form Major.Minor. Each version of the SAML specification set will be construed
so as to document the syntax, semantics, and processing rules of the assertions of the same version.
That is, specification set version 1.0 describes assertion version 1.0, and so on.

2769
2770

There is explicitly NO relationship between the assertion version and the target XML namespace specified
for the schema definitions for that assertion version.

2771

The following processing rules apply:

2772
2773

• A SAML asserting party MUST NOT issue any assertion with an overall Major.Minor assertion
version number not supported by the authority.

2774
2775

• A SAML relying party MUST NOT process any assertion with a major assertion version number notsupported by the relying party.

2776
2777
2778

• A SAML relying party MAY process or MAY reject an assertion whose minor assertion version
number is higher than the minor assertion version number supported by the relying party. However,
all assertions that share a major assertion version number MUST share the same general

129
130

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 65 of 86

2779
2780
2781
2782

processing rules and semantics, and MAY be treated in a uniform way by an implementation. For
example, if a V1.1 assertion shares the syntax of a V1.0 assertion, an implementation MAY treat theassertion as a V1.0 assertion without ill effect. (See Section 4.2.1 for more information about thelikely effects of schema evolution.)

2783

4.1.3 SAML Protocol Version

2784
2785
2786
2787
2788

The various SAML protocols' request and response elements contain an attribute for expressing the major
and minor version of the request or response message using a string of the form Major.Minor. Eachversion of the SAML specification set will be construed so as to document the syntax, semantics, andprocessing rules of the protocol messages of the same version. That is, specification set version 1.0
describes request and response version V1.0, and so on.

2789
2790

There is explicitly NO relationship between the protocol version and the target XML namespace specified
for the schema definitions for that protocol version.

2791
2792

The version numbers used in SAML protocol request and response elements will match for any particularrevision of the SAML specification set.

2793

4.1.3.1 Request Version

2794

The following processing rules apply to requests:

2795
2796

• A SAML requester SHOULD issue requests with the highest request version supported by both the
SAML requester and the SAML responder.

2797
2798
2799

• If the SAML requester does not know the capabilities of the SAML responder, then it SHOULD
assume that the responder supports requests with the highest request version supported by therequester.

2800
2801

• A SAML requester MUST NOT issue a request message with an overall Major.Minor request version
number matching a response version number that the requester does not support.

2802
2803

• A SAML responder MUST reject any request with a major request version number not supported by
the responder.

2804
2805
2806
2807
2808
2809

• A SAML responder MAY process or MAY reject any request whose minor request version number ishigher than the highest supported request version that it supports. However, all requests that sharea major request version number MUST share the same general processing rules and semantics,
and MAY be treated in a uniform way by an implementation. That is, if a V1.1 request shares thesyntax of a V1.0 request, a responder MAY treat the request message as a V1.0 request without ill
effect. (See Section 4.2.1 for more information about the likely effects of schema evolution.)

2810

4.1.3.2 Response Version

2811

The following processing rules apply to responses:

2812
2813

• A SAML responder MUST NOT issue a response message with a response version number higher
than the request version number of the corresponding request message.

2814
2815
2816

• A SAML responder MUST NOT issue a response message with a major response version number
lower than the major request version number of the corresponding request message except toreport the error urn:oasis:names:tc:SAML:2.0:status:RequestVersionTooHigh.

2817
2818
2819
2820

• An error response resulting from incompatible SAML protocol versions MUST result in reporting a
top-level <StatusCode> value of
urn:oasis:names:tc:SAML:2.0:status:VersionMismatch, and MAY result in reporting
one of the following second-level values:

131
132

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 66 of 86

2821
2822
2823

urn:oasis:names:tc:SAML:2.0:status:RequestVersionTooHigh,
urn:oasis:names:tc:SAML:2.0:status:RequestVersionTooLow, or
urn:oasis:names:tc:SAML:2.0:status:RequestVersionDeprecated.

2824

4.1.3.3 Permissible Version Combinations

2825
2826
2827
2828
2829
2830

Assertions of a particular major version appear only in response messages of the same major version, as
permitted by the importation of the SAML assertion namespace into the SAML protocol schema. For
example, a V1.1 assertion MAY appear in a V1.0 response message, and a V1.0 assertion in a V1.1
response message, if the appropriate assertion schema is referenced during namespace importation. But
a V1.0 assertion MUST NOT appear in a V2.0 response message because they are of different major
versions.

2831

4.2 SAML Namespace Version

2832
2833
2834
2835

XML schema documents published as part of the specification set contain one or more target
namespaces into which the type, element, and attribute definitions are placed. Each namespace is distinct
from the others, and represents, in shorthand, the structural and syntactic definitions that make up thatpart of the specification.

2836
2837
2838
2839
2840
2841
2842

The namespace URI references defined by the specification set will generally contain version informationof the form Major.Minor somewhere in the URI. The major and minor version in the URI MUST correspondto the major and minor version of the specification set in which the namespace is first introduced anddefined. This information is not typically consumed by an XML processor, which treats the namespace
opaquely, but is intended to communicate the relationship between the specification set and thenamespaces it defines. This pattern is also followed by the SAML-defined URI-based identifiers that arelisted in Section 8.

2843
2844
2845
2846
2847

As a general rule, implementers can expect the namespaces and the associated schema definitions
defined by a major revision of the specification set to remain valid and stable across minor revisions of thespecification. New namespaces may be introduced, and when necessary, old namespaces replaced, but
this is expected to be rare. In such cases, the older namespaces and their associated definitions should
be expected to remain valid until a major specification set revision.

2848

4.2.1 Schema Evolution

2849
2850
2851
2852
2853
2854
2855

In general, maintaining namespace stability while adding or changing the content of a schema arecompeting goals. While certain design strategies can facilitate such changes, it is complex to predict how
older implementations will react to any given change, making forward compatibility difficult to achieve.
Nevertheless, the right to make such changes in minor revisions is reserved, in the interest of namespacestability. Except in special circumstances (for example, to correct major deficiencies or to fix errors),
implementations should expect forward-compatible schema changes in minor revisions, allowing new
messages to validate against older schemas.

2856
2857
2858
2859
2860

Implementations SHOULD expect and be prepared to deal with new extensions and message types inaccordance with the processing rules laid out for those types. Minor revisions MAY introduce new types
that leverage the extension facilities described in Section 7. Older implementations SHOULD reject suchextensions gracefully when they are encountered in contexts that dictate mandatory semantics. Examples
include new query, statement, or condition types.

133
134

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 67 of 86

2861

5 SAML and XML Signature Syntax and Processing

2862
2863
2864
2865
2866
2867

SAML assertions and SAML protocol request and response messages may be signed, with the following
benefits. An assertion signed by the asserting party supports assertion integrity, authentication of theasserting party to a SAML relying party, and, if the signature is based on the SAML authority’s publicprivate key pair, non-repudiation of origin. A SAML protocol request or response message signed by themessage originator supports message integrity, authentication of message origin to a destination, and, if
the signature is based on the originator's public-private key pair, non-repudiation of origin.

2868
2869
2870
2871
2872
2873
2874
2875
2876

A digital signature is not always required in SAML. For example, in some circumstances, signatures may
be “inherited," such as when an unsigned assertion gains protection from a signature on the containing
protocol response message. "Inherited" signatures should be used with care when the contained object(such as the assertion) is intended to have a non-transitory lifetime. The reason is that the entire context
must be retained to allow validation, exposing the XML content and adding potentially unnecessary
overhead. As another example, the SAML relying party or SAML requester may have obtained an
assertion or protocol message from the SAML asserting party or SAML responder directly (with nointermediaries) through a secure channel, with the asserting party or SAML responder having
authenticated to the relying party or SAML responder by some means other than a digital signature.

2877
2878
2879
2880
2881
2882

Many different techniques are available for "direct" authentication and secure channel establishment
between two parties. The list includes TLS/SSL (see [RFC 2246]/[SSL3]), HMAC, password-based
mechanisms, and so on. In addition, the applicable security requirements depend on the communicating
applications and the nature of the assertion or message transported. It is RECOMMENDED that, in allother contexts, digital signatures be used for assertions and request and response messages.
Specifically:

2883
2884

• A SAML assertion obtained by a SAML relying party from an entity other than the SAML asserting
party SHOULD be signed by the SAML asserting party.

2885
2886

• A SAML protocol message arriving at a destination from an entity other than the originating sender
SHOULD be signed by the sender.

2887
2888
2889
2890

• Profiles MAY specify alternative signature mechanisms such as S/MIME or signed Java objects that
contain SAML documents. Caveats about retaining context and interoperability apply. XML
Signatures are intended to be the primary SAML signature mechanism, but this specification
attempts to ensure compatibility with profiles that may require other mechanisms.

2891
2892

• Unless a profile specifies an alternative signature mechanism, any XML Digital Signatures MUST be
enveloped.

2893

5.1 Signing Assertions

2894
2895

All SAML assertions MAY be signed using XML Signature. This is reflected in the assertion schema as
described in Section 2.

2896

5.2 Request/Response Signing

2897
2898

All SAML protocol request and response messages MAY be signed using XML Signature. This is reflectedin the schema as described in Section 3.

2899

5.3 Signature Inheritance

2900
2901
2902
2903

A SAML assertion may be embedded within another SAML element, such as an enclosing <Assertion>
or a request or response, which may be signed. When a SAML assertion does not contain a<ds:Signature> element, but is contained in an enclosing SAML element that contains a<ds:Signature> element, and the signature applies to the <Assertion> element and all its children,

135
136

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 68 of 86

2904
2905
2906

then the assertion can be considered to inherit the signature from the enclosing element. The resulting
interpretation should be equivalent to the case where the assertion itself was signed with the same key
and signature options.

2907
2908
2909
2910
2911

Many SAML use cases involve SAML XML data enclosed within other protected data structures such as
signed SOAP messages, S/MIME packages, and authenticated SSL connections. SAML profiles MAY
define additional rules for interpreting SAML elements as inheriting signatures or other authentication
information from the surrounding context, but no such inheritance should be inferred unless specifically
identified by the profile.

2912

5.4 XML Signature Profile

2913
2914
2915
2916
2917
2918

The XML Signature specification [XMLSig] calls out a general XML syntax for signing data with flexibility
and many choices. This section details constraints on these facilities so that SAML processors do nothave to deal with the full generality of XML Signature processing. This usage makes specific use of thexs:ID-typed attributes present on the root elements to which signatures can apply, specifically the ID
attribute on <Assertion> and the various request and response elements. These attributes arecollectively referred to in this section as the identifier attributes.

2919
2920
2921

Note that this profile only applies to the use of the <ds:Signature> elements found directly within SAML
assertions, requests, and responses. Other profiles in which signatures appear elsewhere but apply to
SAML content are free to define other approaches.

2922

5.4.1 Signing Formats and Algorithms

2923
2924

XML Signature has three ways of relating a signature to a document: enveloping, enveloped, anddetached.

2925
2926
2927

SAML assertions and protocols MUST use enveloped signatures when signing assertions and protocol
messages. SAML processors SHOULD support the use of RSA signing and verification for public key
operations in accordance with the algorithm identified by http://www.w3.org/2000/09/xmldsig#rsa-sha1.

2928

5.4.2 References

2929
2930
2931
2932

SAML assertions and protocol messages MUST supply a value for the ID attribute on the root element of
the assertion or protocol message being signed. The assertion’s or protocol message's root element may
or may not be the root element of the actual XML document containing the signed assertion or protocol
message (e.g., it might be contained within a SOAP envelope).

2933
2934
2935

Signatures MUST contain a single <ds:Reference> containing a same-document reference to the ID
attribute value of the root element of the assertion or protocol message being signed. For example, if the
ID attribute value is "foo", then the URI attribute in the <ds:Reference> element MUST be "#foo".

2936

5.4.3 Canonicalization Method

2937
2938
2939
2940

SAML implementations SHOULD use Exclusive Canonicalization [Excl-C14N], with or without comments,
both in the <ds:CanonicalizationMethod> element of <ds:SignedInfo>, and as a<ds:Transform> algorithm. Use of Exclusive Canonicalization ensures that signatures created over
SAML messages embedded in an XML context can be verified independent of that context.

2941

5.4.4 Transforms

2942
2943

Signatures in SAML messages SHOULD NOT contain transforms other than the enveloped signaturetransform (with the identifier http://www.w3.org/2000/09/xmldsig#enveloped-signature) or the exclusive

137
138

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 69 of 86

2944
2945

canonicalization transforms (with the identifier http://www.w3.org/2001/10/xml-exc-c14n# or
http://www.w3.org/2001/10/xml-exc-c14n#WithComments).

2946
2947
2948
2949
2950

Verifiers of signatures MAY reject signatures that contain other transform algorithms as invalid. If they donot, verifiers MUST ensure that no content of the SAML message is excluded from the signature. This canbe accomplished by establishing out-of-band agreement as to what transforms are acceptable, or by
applying the transforms manually to the content and reverifying the result as consisting of the same SAML
message.

2951

5.4.5 KeyInfo

2952
2953
2954

XML Signature defines usage of the <ds:KeyInfo> element. SAML does not require the use of<ds:KeyInfo>, nor does it impose any restrictions on its use. Therefore, <ds:KeyInfo> MAY be
absent.

2955

5.4.6 Example

2956
2957

Following is an example of a signed response containing a signed assertion. Line breaks have been
added for readability; the signatures are not valid and cannot be successfully verified.

2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999

<Response
IssueInstant="2003-04-17T00:46:02Z" Version="2.0"
ID="_c7055387-af61-4fce-8b98-e2927324b306"
xmlns="urn:oasis:names:tc:SAML:2.0:protocol"
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"><saml:Issuer>https://www.opensaml.org/IDP"</saml:Issuer><ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:SignedInfo><ds:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><ds:SignatureMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><ds:Reference URI="#_c7055387-af61-4fce-8b98-e2927324b306"><ds:Transforms><ds:Transform
Algorithm="http://www.w3.org/2000/09/xmldsig#envelopedsignature"/><ds:Transform
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"><InclusiveNamespaces PrefixList="#default saml ds xs xsi"
xmlns="http://www.w3.org/2001/10/xml-exc-c14n#"/></ds:Transform></ds:Transforms><ds:DigestMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>TCDVSuG6grhyHbzhQFWFzGrxIPE=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>
x/GyPbzmFEe85pGD3c1aXG4Vspb9V9jGCjwcRCKrtwPS6vdVNCcY5rHaFPYWkf+5
EIYcPzx+pX1h43SmwviCqXRjRtMANWbHLhWAptaK1ywS7gFgsD01qjyen3CP+m3D
w6vKhaqledl0BYyrIzb4KkHO4ahNyBVXbJwqv5pUaE4=</ds:SignatureValue><ds:KeyInfo><ds:X509Data><ds:X509Certificate>
MIICyjCCAjOgAwIBAgICAnUwDQYJKoZIhvcNAQEEBQAwgakxCzAJBgNVBAYTAlVTMRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlzb24xIDAeBgNVBAoTF1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJEaXZpc2lvbiBvZiBJ
bmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBLSSBTZXJ2ZXIgQ0Eg
LS0gMjAwMjA3MDFBMB4XDTAyMDcyNjA3Mjc1MVoXDTA2MDkwNDA3Mjc1MVowgYsx
CzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjESMBAGA1UEBxMJQW5uIEFy

139
140

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 70 of 86

3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065

141
142

Ym9yMQ4wDAYDVQQKEwVVQ0FJRDEcMBoGA1UEAxMTc2hpYjEuaW50ZXJuZXQyLmVk
dTEnMCUGCSqGSIb3DQEJARYYcm9vdEBzaGliMS5pbnRlcm5ldDIuZWR1MIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZSAb2sxvhAXnXVIVTx8vuRay+x50z7GJj
IHRYQgIv6IqaGG04eTcyVMhoekE0b45QgvBIaOAPSZBl13R6+KYiE7x4XAWIrCP+
c2MZVeXeTgV3Yz+USLg2Y1on+Jh4HxwkPFmZBctyXiUr6DxF8rvoP9W7O27rhRjE
pmqOIfGTWQIDAQABox0wGzAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIFoDANBgkq
hkiG9w0BAQQFAAOBgQBfDqEW+OI3jqBQHIBzhujN/PizdN7s/z4D5d3pptWDJf2n
qgi7lFV6MDkhmTvTqBtjmNk3No7v/dnP6Hr7wHxvCCRwubnmIfZ6QZAv2FU78pLX
8I3bsbmRAUg4UP9hH6ABVq4KQKMknxu1xQxLhpR1ylGPdiowMNTrEG8cCx3w/w==</ds:X509Certificate></ds:X509Data></ds:KeyInfo></ds:Signature><Status><StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/></Status><Assertion ID="_a75adf55-01d7-40cc-929f-dbd8372ebdfc"
IssueInstant="2003-04-17T00:46:02Z" Version="2.0"
xmlns="urn:oasis:names:tc:SAML:2.0:assertion"><Issuer>https://www.opensaml.org/IDP</Issuer><ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:SignedInfo><ds:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><ds:SignatureMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><ds:Reference URI="#_a75adf55-01d7-40cc-929f-dbd8372ebdfc"><ds:Transforms><ds:Transform
Algorithm="http://www.w3.org/2000/09/xmldsig#envelopedsignature"/><ds:Transform
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"><InclusiveNamespaces
PrefixList="#default saml ds xs xsi"
xmlns="http://www.w3.org/2001/10/xml-exc-c14n#"/></ds:Transform></ds:Transforms><ds:DigestMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>Kclet6XcaOgOWXM4gty6/UNdviI=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>
hq4zk+ZknjggCQgZm7ea8fI79gJEsRy3E8LHDpYXWQIgZpkJN9CMLG8ENR4Nrw+n
7iyzixBvKXX8P53BTCT4VghPBWhFYSt9tHWu/AtJfOTh6qaAsNdeCyG86jmtp3TD
MwuL/cBUj2OtBZOQMFn7jQ9YB7klIz3RqVL+wNmeWI4=</ds:SignatureValue><ds:KeyInfo><ds:X509Data><ds:X509Certificate>
MIICyjCCAjOgAwIBAgICAnUwDQYJKoZIhvcNAQEEBQAwgakxCzAJBgNVBAYTAlVTMRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlzb24xIDAeBgNVBAoTF1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJEaXZpc2lvbiBvZiBJ
bmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBLSSBTZXJ2ZXIgQ0Eg
LS0gMjAwMjA3MDFBMB4XDTAyMDcyNjA3Mjc1MVoXDTA2MDkwNDA3Mjc1MVowgYsx
CzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjESMBAGA1UEBxMJQW5uIEFy
Ym9yMQ4wDAYDVQQKEwVVQ0FJRDEcMBoGA1UEAxMTc2hpYjEuaW50ZXJuZXQyLmVk
dTEnMCUGCSqGSIb3DQEJARYYcm9vdEBzaGliMS5pbnRlcm5ldDIuZWR1MIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZSAb2sxvhAXnXVIVTx8vuRay+x50z7GJj
IHRYQgIv6IqaGG04eTcyVMhoekE0b45QgvBIaOAPSZBl13R6+KYiE7x4XAWIrCP+
c2MZVeXeTgV3Yz+USLg2Y1on+Jh4HxwkPFmZBctyXiUr6DxF8rvoP9W7O27rhRjE
pmqOIfGTWQIDAQABox0wGzAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIFoDANBgkq
hkiG9w0BAQQFAAOBgQBfDqEW+OI3jqBQHIBzhujN/PizdN7s/z4D5d3pptWDJf2n
qgi7lFV6MDkhmTvTqBtjmNk3No7v/dnP6Hr7wHxvCCRwubnmIfZ6QZAv2FU78pLX
8I3bsbmRAUg4UP9hH6ABVq4KQKMknxu1xQxLhpR1ylGPdiowMNTrEG8cCx3w/w==

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 71 of 86

3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092

143
144

</ds:X509Certificate></ds:X509Data></ds:KeyInfo></ds:Signature><Subject><NameID
Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">scott@example.org</NameID><SubjectConfirmation
Method="urn:oasis:names:tc:SAML:2.0:cm:bearer"/></Subject><Conditions NotBefore="2003-04-17T00:46:02Z"
NotOnOrAfter="2003-04-17T00:51:02Z"><AudienceRestriction><Audience>http://www.opensaml.org/SP</Audience></AudienceRestriction></Conditions><AuthnStatement AuthnInstant="2003-04-17T00:46:00Z"><AuthnContext><AuthnContextClassRef>
urn:oasis:names:tc:SAML:2.0:ac:classes:Password</AuthnContextClassRef></AuthnContext></AuthnStatement></Assertion></Response>

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 72 of 86

3093

6 SAML and XML Encryption Syntax and Processing

3094
3095
3096
3097

Encryption is used as the means to implement confidentiality. The most common motives forconfidentiality are to protect the personal privacy of individuals or to protect organizational secrets forcompetitive advantage or similar reasons. Confidentiality may also be required to ensure the effectivenessof some other security mechanism. For example, a secret password or key may be encrypted.

3098

Several ways of using encryption to confidentially protect all or part of a SAML assertion are provided.
• Communications confidentiality may be provided by mechanisms associated with a particularbinding or profile. For example, the SOAP Binding [SAMLBind] supports the use of SSL/TLS (see[RFC 2246]/[SSL3]) or SOAP Message Security mechanisms for confidentiality.

3099
3100
3101
3102
3103
3104

•

A <SubjectConfirmation> secret can be protected through the use of the <ds:KeyInfo>element within <SubjectConfirmationData>, which permits keys or other secrets to be
encrypted.

3105

•

An entire <Assertion> element may be encrypted, as described in Section 2.3.4.

3106

•

The <BaseID> or <NameID> element may be encrypted, as described in Section 2.2.4.

3107

•

An <Attribute> element may be encrypted, as described in Section 2.7.3.2.

3108

6.1 General Considerations

3109
3110
3111
3112
3113

Encryption of the <Assertion>, <BaseID>, <NameID> and <Attribute> elements is provided by useof XML Encryption [XMLEnc]. Encrypted data and optionally one or more encrypted keys MUST replace
the plaintext information in the same location within the XML instance. The <EncryptedData> element's
Type attribute SHOULD be used and, if it is present, MUST have the value
http://www.w3.org/2001/04/xmlenc#Element.

3114
3115

Any of the algorithms defined for use with XML Encryption MAY be used to perform the encryption. The
SAML schema is defined so that the inclusion of the encrypted data yields a valid instance.

3116

6.2 Combining Signatures and Encryption

3117
3118
3119

Use of XML Encryption and XML Signature MAY be combined. When an assertion is to be signed andencrypted, the following rules apply. A relying party MUST perform signature validation and decryption in
the reverse order that signing and encryption were performed.

3120
3121

•

When a signed <Assertion> element is encrypted, the signature MUST first be calculated andplaced within the <Assertion> element before the element is encrypted.

3122
3123
3124

•

When a <BaseID>, <NameID>, or <Attribute> element is encrypted, the encryption MUST be
performed first and then the signature calculated over the assertion or message containing theencrypted element.

145
146

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 73 of 86

3125

7 SAML Extensibility

3126
3127
3128
3129

SAML supports extensibility in a number of ways, including extending the assertion and protocol schemas.
An example of an application that extends SAML assertions is the Liberty Protocols and SchemaSpecification [LibertyProt]. The following sections explain the extensibility features with SAML assertions
and protocols.

3130
3131

See the SAML Profiles specification [SAMLProf] for information on how to define new profiles, which canbe combined with extensions to put the SAML framework to new uses.

3132

7.1 Schema Extension

3133
3134
3135
3136
3137

Note that elements in the SAML schemas are blocked from substitution, which means that no SAML
elements can serve as the head element of a substitution group. However, SAML types are not defined as
final, so that all SAML types MAY be extended and restricted. As a practical matter, this means that
extensions are typically defined only as types rather than elements, and are included in SAML instancesby means of an xsi:type attribute.

3138
3139

The following sections discuss only elements and types that have been specifically designed to support
extensibility.

3140

7.1.1 Assertion Schema Extension

3141
3142

The SAML assertion schema (see [SAML-XSD]) is designed to permit separate processing of theassertion package and the statements it contains, if the extension mechanism is used for either part.

3143
3144

The following elements are intended specifically for use as extension points in an extension schema; theirtypes are set to abstract, and are thus usable only as the base of a derived type:3145• <BaseID> and BaseIDAbstractType

3146• <Condition> and ConditionAbstractType

3147• <Statement> and StatementAbstractType

3148
3149

•

The following constructs that are directly usable as part of SAML are particularly interesting targets forextension:

3150• <AuthnStatement> and AuthnStatementType

3151• <AttributeStatement> and AttributeStatementType

3152• <AuthzDecisionStatement> and AuthzDecisionStatementType

3153• <AudienceRestriction> and AudienceRestrictionType3154• <ProxyRestriction> and ProxyRestrictionType3155• <OneTimeUse> and OneTimeUseType3156

7.1.2 Protocol Schema Extension

3157
3158
3159

The following SAML protocol elements are intended specifically for use as extension points in an
extension schema; their types are set to abstract, and are thus usable only as the base of a derived
type:

3160

• <Request> and RequestAbstractType

3161• <SubjectQuery> and SubjectQueryAbstractType

147
148

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 74 of 86

3162
3163

The following constructs that are directly usable as part of SAML are particularly interesting targets forextension:

3164• <AuthnQuery> and AuthnQueryType

3165• <AuthzDecisionQuery> and AuthzDecisionQueryType

3166• <AttributeQuery> and AttributeQueryType

3167• StatusResponseType3168

7.2 Schema Wildcard Extension Points

3169
3170
3171

The SAML schemas use wildcard constructs in some locations to allow the use of elements and attributes
from arbitrary namespaces, which serves as a built-in extension point without requiring an extension
schema.

3172

7.2.1 Assertion Extension Points

3173

The following constructs in the assertion schema allow constructs from arbitrary namespaces within them:

3174
3175

• <SubjectConfirmationData>: Uses xs:anyType, which allows any sub-elements andattributes.

3176• <AuthnContextDecl>: Uses xs:anyType, which allows any sub-elements and attributes.

3177• <AttributeValue>: Uses xs:anyType, which allows any sub-elements and attributes.

3178
3179

• <Advice> and AdviceType: In addition to SAML-native elements, allows elements from othernamespaces with lax schema validation processing.

3180

The following constructs in the assertion schema allow arbitrary global attributes:

3181• <Attribute> and AttributeType3182

7.2.2 Protocol Extension Points

3183

The following constructs in the protocol schema allow constructs from arbitrary namespaces within them:

3184
3185

• <Extensions> and ExtensionsType: Allows elements from other namespaces with lax schema
validation processing.

3186
3187

• <StatusDetail> and StatusDetailType: Allows elements from other namespaces with lax
schema validation processing.

3188
3189
3190

• <ArtifactResponse> and ArtifactResponseType: Allows elements from any namespaces withlax schema validation processing. (It is specifically intended to carry a SAML request or response
message element, however.)3191

7.3 Identifier Extension

3192
3193
3194
3195
3196
3197

SAML uses URI-based identifiers for a number of purposes, such as status codes and name identifier
formats, and defines some identifiers that MAY be used for these purposes; most are listed in Section 8.
However, it is always possible to define additional URI-based identifiers for these purposes. It is
RECOMMENDED that these additional identifiers be defined in a formal profile of use. In no case should
the meaning of a given URI used as such an identifier significantly change, or be used to mean two
different things.

149
150

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 75 of 86

3198

8 SAML-Defined Identifiers

3199
3200

The following sections define URI-based identifiers for common resource access actions, subject nameidentifier formats, and attribute name formats.

3201
3202
3203
3204

Where possible an existing URN is used to specify a protocol. In the case of IETF protocols, the URN of
the most current RFC that specifies the protocol is used. URI references created specifically for SAML
have one of the following stems, according to the specification set version in which they were first
introduced:

3205
3206
3207

urn:oasis:names:tc:SAML:1.0:
urn:oasis:names:tc:SAML:1.1:
urn:oasis:names:tc:SAML:2.0:3208

8.1 Action Namespace Identifiers

3209
3210

The following identifiers MAY be used in the Namespace attribute of the <Action> element to refer tocommon sets of actions to perform on resources.

3211

8.1.1 Read/Write/Execute/Delete/Control

3212

URI: urn:oasis:names:tc:SAML:1.0:action:rwedc

3213

Defined actions:

3214

Read Write Execute Delete Control

3215

These actions are interpreted as follows:

3216

Read

3217
3218
3219
3220
3221
3222
3223
3224

The subject may read the resource.
Write
The subject may modify the resource.
ExecuteThe subject may execute the resource.
DeleteThe subject may delete the resource.
Control

3225

The subject may specify the access control policy for the resource.

3226

8.1.2 Read/Write/Execute/Delete/Control with Negation

3227

URI: urn:oasis:names:tc:SAML:1.0:action:rwedc-negation

3228

Defined actions:

3229

Read Write Execute Delete Control ~Read ~Write ~Execute ~Delete ~Control

3230
3231
3232
3233

The actions specified in Section 8.1.1 are interpreted in the same manner described there. Actions
prefixed with a tilde (~) are negated permissions and are used to affirmatively specify that the statedpermission is denied. Thus a subject described as being authorized to perform the action ~Read isaffirmatively denied read permission.

151
152

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 76 of 86

3234

A SAML authority MUST NOT authorize both an action and its negated form.

3235

8.1.3 Get/Head/Put/Post

3236

URI: urn:oasis:names:tc:SAML:1.0:action:ghpp

3237

Defined actions:

3238

GET HEAD PUT POST

3239
3240

These actions bind to the corresponding HTTP operations. For example a subject authorized to performthe GET action on a resource is authorized to retrieve it.

3241
3242
3243
3244

The GET and HEAD actions loosely correspond to the conventional read permission and the PUT and POST
actions to the write permission. The correspondence is not exact however since an HTTP GET operation
may cause data to be modified and a POST operation may cause modification to a resource other thanthe one specified in the request. For this reason a separate Action URI reference specifier is provided.

3245

8.1.4 UNIX File Permissions

3246

URI: urn:oasis:names:tc:SAML:1.0:action:unix

3247

The defined actions are the set of UNIX file access permissions expressed in the numeric (octal) notation.

3248

The action string is a four-digit numeric code:

3249

extended user group world

3250

Where the extended access permission has the value3251+2 if sgid is set

3252+4 if suid is set

3253

The user group and world access permissions have the value3254+1 if execute permission is granted

3255+2 if write permission is granted

3256+4 if read permission is granted

3257
3258

For example, 0754 denotes the UNIX file access permission: user read, write, and execute; group readand execute; and world read.

3259

8.2 Attribute Name Format Identifiers

3260
3261

The following identifiers MAY be used in the NameFormat attribute defined on the AttributeType complex
type to refer to the classification of the attribute name for purposes of interpreting the name.

3262

8.2.1 Unspecified

3263

URI: urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified

3264

The interpretation of the attribute name is left to individual implementations.

153
154

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 77 of 86

3265

8.2.2 URI Reference

3266

URI: urn:oasis:names:tc:SAML:2.0:attrname-format:uri

3267
3268
3269

The attribute name follows the convention for URI references [RFC 2396], for example as used in XACML[XACML] attribute identifiers. The interpretation of the URI content or naming scheme is applicationspecific. See [SAMLProf] for attribute profiles that make use of this identifier.

3270

8.2.3 Basic

3271

URI: urn:oasis:names:tc:SAML:2.0:attrname-format:basic

3272
3273
3274

The class of strings acceptable as the attribute name MUST be drawn from the set of values belonging to
the primitive type xs:Name as defined in [Schema2] Section 3.3.6. See [SAMLProf] for attribute profiles
that make use of this identifier.

3275

8.3 Name Identifier Format Identifiers

3276
3277
3278

The following identifiers MAY be used in the Format attribute of the <NameID>, <NameIDPolicy>, or<Issuer> elements (see Section 2.2) to refer to common formats for the content of the elements and theassociated processing rules, if any.

3279
3280

Note: Several identifiers that were deprecated in SAML V1.1 have been removed for
SAML V2.0.

3281

8.3.1 Unspecified

3282

URI: urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified

3283

The interpretation of the content of the element is left to individual implementations.

3284

8.3.2 Email Address

3285

URI: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

3286
3287
3288
3289

Indicates that the content of the element is in the form of an email address, specifically "addr-spec" asdefined in IETF RFC 2822 [RFC 2822] Section 3.4.1. An addr-spec has the form local-part@domain. Notethat an addr-spec has no phrase (such as a common name) before it, has no comment (text surroundedin parentheses) after it, and is not surrounded by "<" and ">".

3290

8.3.3 X.509 Subject Name

3291

URI: urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName

3292
3293
3294
3295

Indicates that the content of the element is in the form specified for the contents of the<ds:X509SubjectName> element in the XML Signature Recommendation [XMLSig]. Implementors
should note that the XML Signature specification specifies encoding rules for X.509 subject names thatdiffer from the rules given in IETF RFC 2253 [RFC 2253].

3296

8.3.4 Windows Domain Qualified Name

3297

URI: urn:oasis:names:tc:SAML:1.1:nameid-format:WindowsDomainQualifiedName

155
156

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 78 of 86

3298
3299
3300

Indicates that the content of the element is a Windows domain qualified name. A Windows domain
qualified user name is a string of the form "DomainName\UserName". The domain name and "\" separator
MAY be omitted.

3301

8.3.5 Kerberos Principal Name

3302

URI: urn:oasis:names:tc:SAML:2.0:nameid-format:kerberos

3303
3304
3305

Indicates that the content of the element is in the form of a Kerberos principal name using the format
name[/instance]@REALM. The syntax, format and characters allowed for the name, instance, andrealm are described in IETF RFC 1510 [RFC 1510].

3306

8.3.6 Entity Identifier

3307

URI: urn:oasis:names:tc:SAML:2.0:nameid-format:entity

3308
3309
3310
3311
3312
3313
3314

Indicates that the content of the element is the identifier of an entity that provides SAML-based services(such as a SAML authority, requester, or responder) or is a participant in SAML profiles (such as a service
provider supporting the browser SSO profile). Such an identifier can be used in the <Issuer> element to
identify the issuer of a SAML request, response, or assertion, or within the <NameID> element to makeassertions about system entities that can issue SAML requests, responses, and assertions. It can also be
used in other elements and attributes whose purpose is to identify a system entity in various protocol
exchanges.

3315
3316

The syntax of such an identifier is a URI of not more than 1024 characters in length. It is
RECOMMENDED that a system entity use a URL containing its own domain name to identify itself.

3317

The NameQualifier, SPNameQualifier, and SPProvidedID attributes MUST be omitted.

3318

8.3.7 Persistent Identifier

3319

URI: urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

3320
3321
3322
3323
3324
3325

Indicates that the content of the element is a persistent opaque identifier for a principal that is specific toan identity provider and a service provider or affiliation of service providers. Persistent name identifiers
generated by identity providers MUST be constructed using pseudo-random values that have no
discernible correspondence with the subject's actual identifier (for example, username). The intent is tocreate a non-public, pair-wise pseudonym to prevent the discovery of the subject's identity or activities.
Persistent name identifier values MUST NOT exceed a length of 256 characters.

3326
3327
3328
3329
3330
3331
3332

The element's NameQualifier attribute, if present, MUST contain the unique identifier of the identity
provider that generated the identifier (see Section 8.3.6). It MAY be omitted if the value can be derived
from the context of the message containing the element, such as the issuer of a protocol message or an
assertion containing the identifier in its subject. Note that a different system entity might later issue its own
protocol message or assertion containing the identifier; the NameQualifier attribute does not change inthis case, but MUST continue to identify the entity that originally created the identifier (and MUST NOT beomitted in such a case).

3333
3334
3335
3336

The element's SPNameQualifier attribute, if present, MUST contain the unique identifier of the service
provider or affiliation of providers for whom the identifier was generated (see Section 8.3.6). It MAY be
omitted if the element is contained in a message intended only for consumption directly by the service
provider, and the value would be the unique identifier of that service provider.

3337
3338
3339

The element's SPProvidedID attribute MUST contain the alternative identifier of the principal mostrecently set by the service provider or affiliation, if any (see Section 3.6). If no such identifier has been
established, then the attribute MUST be omitted.

157
158

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 79 of 86

3340
3341
3342
3343
3344

Persistent identifiers are intended as a privacy protection mechanism; as such they MUST NOT be sharedin clear text with providers other than the providers that have established the shared identifier.
Furthermore, they MUST NOT appear in log files or similar locations without appropriate controls andprotections. Deployments without such requirements are free to use other kinds of identifiers in their
SAML exchanges, but MUST NOT overload this format with persistent but non-opaque values

3345
3346
3347
3348
3349

Note also that while persistent identifiers are typically used to reflect an account linking relationshipbetween a pair of providers, a service provider is not obligated to recognize or make use of the long term
nature of the persistent identifier or establish such a link. Such a "one-sided" relationship is not discernibly
different and does not affect the behavior of the identity provider or any processing rules specific topersistent identifiers in the protocols defined in this specification.

3350
3351
3352
3353
3354
3355
3356

Finally, note that the NameQualifier and SPNameQualifier attributes indicate directionality ofcreation, but not of use. If a persistent identifier is created by a particular identity provider, theNameQualifier attribute value is permanently established at that time. If a service provider that receives
such an identifier takes on the role of an identity provider and issues its own assertion containing that
identifier, the NameQualifier attribute value does not change (and would of course not be omitted). It
might alternatively choose to create its own persistent identifier to represent the principal and link the twovalues. This is a deployment decision.

3357

8.3.8 Transient Identifier

3358

URI: urn:oasis:names:tc:SAML:2.0:nameid-format:transient

3359
3360
3361
3362

Indicates that the content of the element is an identifier with transient semantics and SHOULD be treatedas an opaque and temporary value by the relying party. Transient identifier values MUST be generated inaccordance with the rules for SAML identifiers (see Section 1.3.4), and MUST NOT exceed a length of
256 characters.

3363
3364
3365

The NameQualifier and SPNameQualifier attributes MAY be used to signify that the identifier
represents a transient and temporary pair-wise identifier. In such a case, they MAY be omitted inaccordance with the rules specified in Section 8.3.7.

3366

8.4 Consent Identifiers

3367
3368
3369

The following identifiers MAY be used in the Consent attribute defined on the RequestAbstractType andStatusResponseType complex types to communicate whether a principal gave consent, and under what
conditions, for the message.

3370

8.4.1 Unspecified

3371

URI: urn:oasis:names:tc:SAML:2.0:consent:unspecified

3372

No claim as to principal consent is being made.

3373

8.4.2 Obtained

3374

URI: urn:oasis:names:tc:SAML:2.0:consent:obtained

3375

Indicates that a principal’s consent has been obtained by the issuer of the message.

3376

8.4.3 Prior

3377

URI: urn:oasis:names:tc:SAML:2.0:consent:prior

159
160

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 80 of 86

3378
3379

Indicates that a principal’s consent has been obtained by the issuer of the message at some point prior to
the action that initiated the message.

3380

8.4.4 Implicit

3381

URI: urn:oasis:names:tc:SAML:2.0:consent:current-implicit

3382
3383
3384
3385

Indicates that a principal’s consent has been implicitly obtained by the issuer of the message during theaction that initiated the message, as part of a broader indication of consent. Implicit consent is typicallymore proximal to the action in time and presentation than prior consent, such as part of a session ofactivities.

3386

8.4.5 Explicit

3387

URI: urn:oasis:names:tc:SAML:2.0:consent:current-explicit

3388
3389

Indicates that a principal’s consent has been explicitly obtained by the issuer of the message during theaction that initiated the message.

3390

8.4.6 Unavailable

3391

URI: urn:oasis:names:tc:SAML:2.0:consent:unavailable

3392

Indicates that the issuer of the message did not obtain consent.

3393

8.4.7 Inapplicable

3394

URI: urn:oasis:names:tc:SAML:2.0:consent:inapplicable

3395

Indicates that the issuer of the message does not believe that they need to obtain or report consent.

161
162

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 81 of 86

3396

9 References

3397

The following works are cited in the body of this specification.

3398

9.1 Normative References

3399
3400

[Excl-C14N]

J. Boyer et al. Exclusive XML Canonicalization Version 1.0. World Wide Web
Consortium, July 2002. See http://www.w3.org/TR/xml-exc-c14n/.

3401
3402
3403

[Schema1]

H. S. Thompson et al. XML Schema Part 1: Structures. World Wide Web
Consortium Recommendation, May 2001. See http://www.w3.org/TR/xmlschema1/. Note that this specification normatively references [Schema2], listed below.

3404
3405

[Schema2]

P. V. Biron et al. XML Schema Part 2: Datatypes. World Wide Web Consortium
Recommendation, May 2001. See http://www.w3.org/TR/xmlschema-2/.

3406
3407

[XML]

T. Bray, et al. Extensible Markup Language (XML) 1.0 (Second Edition). World
Wide Web Consortium, October 2000. See http://www.w3.org/TR/REC-xml.

3408
3409
3410

[XMLEnc]

D. Eastlake et al. XML Encryption Syntax and Processing. World Wide Web
Consortium. See http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/. Notethat this specification normatively references [XMLEnc-XSD], listed below.

3411
3412

[XMLEnc-XSD]

XML Encryption Schema. World Wide Web Consortium. See
http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/xenc-schema.xsd.

3413
3414

[XMLNS]

T. Bray et al. Namespaces in XML. World Wide Web Consortium, January 1999.
See http://www.w3.org/TR/REC-xml-names.

3415
3416
3417

[XMLSig]

D. Eastlake et al. XML-Signature Syntax and Processing. World Wide Web
Consortium, February 2002. See http://www.w3.org/TR/xmldsig-core/. Note that
this specification normatively references [XMLSig-XSD], listed below.

3418
3419
3420

[XMLSig-XSD]

XML Signature Schema. World Wide Web Consortium. See
http://www.w3.org/TR/2000/CR-xmldsig-core-20001031/xmldsig-coreschema.xsd.

3421

9.2 Non-Normative References

3422
3423
3424
3425

[LibertyProt]

J. Beatty et al. Liberty Protocols and Schema Specification Version 1.1. Liberty
Alliance Project, January 2003. See
http://www.projectliberty.org/specs/archive/v1_1/liberty-architecture-protocolsschema-v1.1.pdf.

3426
3427

[RFC 1510]

J. Kohl, C. Neuman. The Kerberos Network Authentication Requestor (V5). IETF
RFC 1510, September 1993. See http://www.ietf.org/rfc/rfc1510.txt.

3428
3429

[RFC 2119]

S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. IETF
RFC 2119, March 1997. See http://www.ietf.org/rfc/rfc2119.txt.

3430
3431

[RFC 2246]

T. Dierks, C. Allen. The TLS Protocol Version 1.0. IETF RFC 2246, January 1999.
See http://www.ietf.org/rfc/rfc2246.txt.

3432
3433
3434

[RFC 2253]

M. Wahl et al. Lightweight Directory Access Protocol (v3): UTF-8 String
Representation of Distinguished Names. IETF RFC 2253, December 1997. See
http://www.ietf.org/rfc/rfc2253.txt.

3435
3436

[RFC 2396]

T. Berners-Lee et al. Uniform Resource Identifiers (URI): Generic Syntax. IETF
RFC 2396, August, 1998. See http://www.ietf.org/rfc/rfc2396.txt.

3437
3438

[RFC 2822]

P. Resnick. Internet Message Format. IETF RFC 2822, April 2001. See
http://www.ietf.org/rfc/rfc2822.txt.

163
164

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 82 of 86

3439
3440

[RFC 3075]

D. Eastlake, J. Reagle, D. Solo. XML-Signature Syntax and Processing. IETF
RFC 3075, March 2001. See http://www.ietf.org/rfc/rfc3075.txt.

3441
3442

[RFC 3513]

R. Hinden, S.Deering, Internet Protocol Version 6 (IPv6) Addressing Architecture.
IETF RFC 3513, April 2003. See http://www.ietf.org/rfc/rfc3513.txt.

3443
3444
3445

[SAMLAuthnCxt]

J. Kemp et al. Authentication Context for the OASIS Security Assertion Markup
Language (SAML) V2.0. OASIS SSTC, March 2005. Document ID saml-authncontext-2.0-os. See http://www.oasis-open.org/committees/security/.

3446
3447
3448

[SAMLBind]

S. Cantor et al. Bindings for the OASIS Security Assertion Markup Language(SAML) V2.0. OASIS SSTC, March 2005. Document ID saml-bindings-2.0-os.
See http://www.oasis-open.org/committees/security/.

3449
3450
3451

[SAMLConform]

P. Mishra et al. Conformance Requirements for the OASIS Security Assertion
Markup Language (SAML) V2.0. OASIS SSTC, March 2005. Document ID samlconformance-2.0-os. http://www.oasis-open.org/committees/security/.

3452
3453
3454

[SAMLGloss]

J. Hodges et al. Glossary for the OASIS Security Assertion Markup Language(SAML) V2.0. OASIS SSTC, March 2005. Document ID saml-glossary-2.0-os.
See http://www.oasis-open.org/committees/security/.

3455
3456
3457

[SAMLMeta]

S. Cantor et al. Metadata for the OASIS Security Assertion Markup Language(SAML) V2.0. OASIS SSTC, March 2005. Document ID saml-metadata-2.0-os.
See http://www.oasis-open.org/committees/security/.

3458
3459
3460

[SAMLP-XSD]

S. Cantor et al. SAML protocols schema. OASIS SSTC, March 2005. Document
ID saml-schema-protocol-2.0. See http://www.oasisopen.org/committees/security/.

3461
3462
3463

[SAMLProf]

S. Cantor et al. Profiles for the OASIS Security Assertion Markup Language(SAML) V2.0. OASIS SSTC, March 2005. Document ID saml-profiles-2.0-os. See
http://www.oasis-open.org/committees/security/.

3464
3465
3466
3467

[SAMLSecure]

F. Hirsch et al. Security and Privacy Considerations for the OASIS Security
Assertion Markup Language (SAML) V2.0. OASIS SSTC, March 2005. Document
ID saml-sec-consider-2.0-os. See http://www.oasisopen.org/committees/security/.

3468
3469
3470

[SAMLTechOvw]

J. Hughes et al. SAML Technical Overview. OASIS, February 2005. Document ID
sstc-saml-tech-overview-2.0-draft-03. See http://www.oasisopen.org/committees/security/.

3471
3472
3473

[SAML-XSD]

S. Cantor et al., SAML assertions schema. OASIS SSTC, March 2005. Document
ID saml-schema-assertion-2.0. See http://www.oasisopen.org/committees/security/.

3474
3475

[SSL3]

A. Frier et al. The SSL 3.0 Protocol. Netscape Communications Corp, November
1996.

3476
3477

[UNICODE-C]

M. Davis, M. J. Dürst. Unicode Normalization Forms. UNICODE Consortium,
March 2001. See http://www.unicode.org/unicode/reports/tr15/tr15-21.html.

3478
3479

[W3C-CHAR]

M. J. Dürst. Requirements for String Identity Matching and String Indexing. World
Wide Web Consortium, July 1998. See http://www.w3.org/TR/WD-charreq.

3480
3481
3482

[W3C-CharMod]

M. J. Dürst. Character Model for the World Wide Web 1.0: Normalization. World
Wide Web Consortium, February 2004. See http://www.w3.org/TR/charmodnorm/.

3483
3484

[XACML]eXtensible Access Control Markup Language (XACML), product of the OASISXACML TC. See http://www.oasis-open.org/committees/xacml.

3485
3486

[XML-ID]

J. Marsh et al. xml:id Version 1.0, World Wide Web Consortium, April 2004. See
http://www.w3.org/TR/xml-id/.

165
166

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 83 of 86

3487

Appendix A. Acknowledgments

3488
3489

The editors would like to acknowledge the contributions of the OASIS Security Services TechnicalCommittee, whose voting members at the time of publication were:

3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528

167
168

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

Conor Cahill, AOL
John Hughes, Atos Origin
Hal Lockhart, BEA Systems
Mike Beach, Boeing
Rebekah Metz, Booz Allen Hamilton
Rick Randall, Booz Allen Hamilton
Ronald Jacobson, Computer Associates
Gavenraj Sodhi, Computer Associates
Thomas Wisniewski, Entrust
Carolina Canales-Valenzuela, Ericsson
Dana Kaufman, Forum Systems
Irving Reid, Hewlett-Packard
Guy Denton, IBM
Heather Hinton, IBM
Maryann Hondo, IBM
Michael McIntosh, IBM
Anthony Nadalin, IBM
Nick Ragouzis, Individual
Scott Cantor, Internet2
Bob Morgan, Internet2
Peter Davis, Neustar
Jeff Hodges, Neustar
Frederick Hirsch, Nokia
Senthil Sengodan, Nokia
Abbie Barbir, Nortel Networks
Scott Kiester, Novell
Cameron Morris, Novell
Paul Madsen, NTT
Steve Anderson, OpenNetwork
Ari Kermaier, Oracle
Vamsi Motukuru, Oracle
Darren Platt, Ping Identity
Prateek Mishra, Principal Identity
Jim Lien, RSA Security
John Linn, RSA Security
Rob Philpott, RSA Security
Dipak Chopra, SAP
Jahan Moreh, Sigaba
Bhavna Bhatnagar, Sun Microsystems

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 84 of 86

3529
3530
3531
3532

•
•
•
•

Eve Maler, Sun Microsystems
Ronald Monzillo, Sun Microsystems
Emily Xu, Sun Microsystems
Greg Whitehead, Trustgenix

3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563

The editors also would like to acknowledge the following former SSTC members for their contributions tothis or previous versions of the OASIS Security Assertions Markup Language Standard:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

Stephen Farrell, Baltimore Technologies
David Orchard, BEA Systems
Krishna Sankar, Cisco Systems
Zahid Ahmed, CommerceOne
Tim Alsop, CyberSafe Limited
Carlisle Adams, Entrust
Tim Moses, Entrust
Nigel Edwards, Hewlett-Packard
Joe Pato, Hewlett-Packard
Bob Blakley, IBM
Marlena Erdos, IBM
Marc Chanliau, Netegrity
Chris McLaren, Netegrity
Lynne Rosenthal, NISTMark Skall, NISTCharles Knouse, Oblix
Simon Godik, Overxeer
Charles Norwood, SAIC
Evan Prodromou, Securant
Robert Griffin, RSA Security (former editor)
Sai Allarvarpu, Sun Microsystems
Gary Ellison, Sun Microsystems
Chris Ferris, Sun Microsystems
Mike Myers, Traceroute Security
Phillip Hallam-Baker, VeriSign (former editor)
James Vanderbeek, Vodafone
Mark O’Neill, Vordel
Tony Palmer, Vordel

3564
3565
3566
3567
3568

169
170

Finally, the editors wish to acknowledge the following people for their contributions of material used as
input to the OASIS Security Assertions Markup Language specifications:• Thomas Gross, IBM• Birgit Pfitzmann, IBMsaml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 85 of 86

3569

Appendix B. Notices

3570
3571
3572
3573
3574
3575
3576
3577

OASIS takes no position regarding the validity or scope of any intellectual property or other rights thatmight be claimed to pertain to the implementation or use of the technology described in this document or
the extent to which any license under such rights might or might not be available; neither does it represent
that it has made any effort to identify any such rights. Information on OASIS's procedures with respect torights in OASIS specifications can be found at the OASIS website. Copies of claims of rights madeavailable for publication and any assurances of licenses to be made available, or the result of an attempt
made to obtain a general license or permission for the use of such proprietary rights by implementors orusers of this specification, can be obtained from the OASIS Executive Director.

3578
3579
3580

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, orother proprietary rights which may cover technology that may be required to implement this specification.
Please address the information to the OASIS Executive Director.

3581

Copyright © OASIS Open 2005. All Rights Reserved.

3582
3583
3584
3585
3586
3587
3588
3589

This document and translations of it may be copied and furnished to others, and derivative works thatcomment on or otherwise explain it or assist in its implementation may be prepared, copied, published anddistributed, in whole or in part, without restriction of any kind, provided that the above copyright notice andthis paragraph are included on all such copies and derivative works. However, this document itself may
not be modified in any way, such as by removing the copyright notice or references to OASIS, except asneeded for the purpose of developing OASIS specifications, in which case the procedures for copyrights
defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it
into languages other than English.

3590
3591

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors
or assigns.

3592
3593
3594
3595

This document and the information contained herein is provided on an “AS IS” basis and OASISDISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANYWARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

171
172

saml-core-2.0-os
Copyright © OASIS Open 2005. All Rights Reserved.

15 March 2005
Page 86 of 86