Web Services Security
X.509 Certificate Token Profile 1.1
OASIS Standard Specification, 251
February August 2006
OASIS Identifier:
wss-v1.1-spec-oserrata-X509TokenProfile
Document Location:
http://docs.oasis-open.org/wss/v1.1/
Technical Committee:
Web Service Security (WSS)
Chairs:
Kelvin Lawrence, IBM
Chris
Kaler, Microsoft
Editors:
Anthony Nadalin, IBM
Chris
Kaler, Microsoft
Ronald
Monzillo, Sun
Phillip Hallam-Baker, Verisign
Abstract:
This document describes how to use X.509
Certificates with the Web Services Security:
Status:
This is an OASIS Standard document produced
by the Web Services Security Technical Committee. It was approved by the OASIS
membership on 1 February 2006. Check the current location noted above for possible
errata to this document.
Technical Committee members should send comments on
this specification to the technical Committee’s email list. Others should send
comments to the Technical Committee by using the “Send A Comment” button on the
Technical Committee’s web page at www.oasisopen.org/committees/wss.
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 the Intellectual Property Rights section of the WS-Security TC web page (http://www.oasis-open.org/committees/wss/ipr.php).
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might 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 vailable; neither does it represent that it has made any effort to identify any such rights. Information on
OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available 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 or users of this specification, can be obtained from the OASIS Executive Director. OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
Copyright (C) OASIS Open 2002-2006. All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this 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 as needed 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.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS has been notified of intellectual property rights claimed in regard to some or all of the contents of this specification. For more information consult the online list of claimed rights.
This section is non-normative.
Table of Contents
1 Introduction (Non-Normative)
2 Notations and Terminology (Normative)
3.1.2
X509PKIPathv1 Token Type
3.2.1
Reference to an X.509 Subject Key Identifier
3.2.2
Reference to a Security Token
3.2.3
Reference to an Issuer and Serial Number
3.3.2
Reference to a Binary Security Token
3.3.3
Reference to an Issuer and Serial Number
4 Threat Model and Countermeasures (Non-Normative)
This specification describes the use of the X.509
authentication framework with the Web Services Security:
An X.509 certificate specifies a binding between a public key and a set of attributes that includes (at least) a subject name, issuer name, serial number and validity interval. This binding may be subject to subsequent revocation advertised by mechanisms that include issuance of CRLs, OCSP tokens or mechanisms that are outside the X.509 framework, such as XKMS.
An X.509 certificate may be used to validate a public key that may be used to authenticate a SOAP message or to identify the public key with a SOAP message that has been encrypted.
Note that Sections 2.1, 2.2, all of 3, and indicated parts of 5 are normative. All other sections are non-normative.
2
Notations and
Terminology (Normative)
This section specifies the notations, namespaces and terminology used in this specification.
2.1 Notational
Conventions
The keywords "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "
When describing abstract data models, this specification uses the notational convention used by the XML Infoset. Specifically, abstract property names always appear in square brackets (e.g., [some property]).
When describing concrete XML schemas, this specification
uses a convention where each member of an element’s [children] or [attributes]
property is described using an XPath-like notation (e.g.,
/x:MyHeader/x:SomeProperty/@value1). The
use of {any} indicates the presence of an element wildcard (<xs:any/>).
The use of @{any} indicates the presence of an attribute wildcard
(<xs:anyAttribute/>).
2.2 Namespaces
Namespace URIs (of the general form "some-URI") represents some application-dependent or context-dependent URI as defined in RFC 3986 [URI]. This specification is designed to work with the general SOAP [SOAP11, SOAP12] message structure and message processing model, and should be applicable to any version of SOAP. The current SOAP 1.1 namespace URI is used herein to provide detailed examples, but there is no intention to limit the applicability of this specification to a single version of SOAP.
The namespaces used in this document are shown in the following table (note that for brevity, the examples use the prefixes listed below but do not include the URIs – those listed below are assumed).
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd
The following namespace prefixes are used in this document:
|
Prefix |
Namespace |
|
S11 |
|
|
S12 |
|
|
ds |
http://www.w3.org/2000/09/xmldsig#
|
|
xenc |
http://www.w3.org/2001/04/xmlenc#
|
|
wsse |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd |
|
wsse11 |
http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd |
|
wsu |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd |
Table 1- Namespace prefixes
URI
fragments defined in this specification are relative to the following base URI unless
otherwise stated:
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0
The following table lists the full URI for each URI fragment referred to in this specification.
|
URI Fragment |
Full URI |
|||
|
#Base64Binary |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary |
|||
|
#STR-Transform |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform |
|||
|
#PKCS7 |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#PKCS7 |
|||
|
#X509v3 |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3 |
|||
|
|
|
|||
|
#X509SubjectKeyIdentifier |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier |
|||
2.3 Terminology
This specification adopts the terminology defined in Web
Services Security:
Readers are presumed to be familiar with the definitions of terms in the Internet Security Glossary [Glossary].
This specification
describes the syntax and processing rules for the use of the X.509
authentication framework with the Web Services Security:
3.1 Token types
This profile defines
the syntax of, and processing rules for, three types of binary security token using
the
If the ValueType
attribute is missing, the receiver may interpret it either based on a prior
agreement or by parsing the content.
|
Token |
ValueType |
Description |
|||
|
Single certificate |
#X509v3 |
An X.509 v3 certificate capable of signature-verification
at a minimum |
|||
|
|