Web Services Security:
SOAP Message Security 1.1
(WS-Security 2004)

OASIS Public Review Draft - 28 June 2005

OASIS identifier:

{product-productVersion-artifactType-stage-descriptiveName-revision.form (Word) (PDF) (HTML)}

Location:

http://docs.oasis-open.org/wss/2005/xx/wss-v1.1-spec-pr-SOAPMessageSecurity-01

Technical Commitee:

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 specification describes enhancements to SOAP messaging to provide message integrity and confidentiality.  The specified mechanisms can be used to accommodate a wide variety of security models and encryption technologies.

 

This specification also provides a general-purpose mechanism for associating security tokens with message content.  No specific type of security token is required, the specification is designed to be extensible (i.e.. support multiple security token formats).  For example, a client might provide one format for proof of identity and provide another format for proof that they have a particular business certification.

 

Additionally, this specification describes how to encode binary security tokens, a framework for XML-based tokens, and how to include opaque encrypted keys.  It also includes extensibility mechanisms that can be used to further describe the characteristics of the tokens that are included with a message.

Status:

This is a technical committee document submitted for consideration by the OASIS Web Services Security (WSS) technical committee. Please send comments to the editors. If you are on the wss@lists.oasis-open.org list for committee members, send comments there. If you are not on that list, subscribe to the wss-comment@lists.oasis-open.org list and send comments there. To subscribe, send an email message to wss-comment-request@lists.oasis-open.org with the word "subscribe" as the body of the message. For patent disclosure information that may be essential to the implementation of this specification, and any offers of licensing terms, refer to the Intellectual Property Rights section of the OASIS Web Services Security Technical Committee (WSS TC) web page at http://www.oasis-open.org/committees/wss/ipr.php.  General OASIS IPR information can be found at http://www.oasis-open.org/who/intellectualproperty.shtml.


 

Notices

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 available; 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 implementers 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 © OASIS Open 2002-2005. 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 does 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.

 

This section is non-normative.


Table of Contents

1      Introduction. 7

1.1 Goals and Requirements. 7

1.1.1 Requirements. 87

1.1.2 Non-Goals. 8

2      Notations and Terminology. 9

2.1 Notational Conventions. 9

2.2 Namespaces. 9

2.3 Acronyms and Abbreviations. 10

2.4 Terminology. 10

2.5 Note on Examples. 12

3      Message Protection Mechanisms. 13

3.1 Message Security Model 13

3.2 Message Protection. 13

3.3 Invalid or Missing Claims. 14

3.4 Example. 14

4      ID References. 16

4.1 Id Attribute. 16

4.2 Id Schema. 16

5      Security Header 18

6      Security Tokens. 20

6.1 Attaching Security Tokens