Document Details     TC Member Document View
Name * (1MB)
Description This zip file contains the WS-SecurityPolicy Examples 1.0 document plus sample message traces from an internal ws-sx virtual Interop conducted to validate several use cases from the document.
The following is from the document abstract:
This document contains examples of how to set up WS-SecurityPolicy [WSSP] policies for a variety of common token types that are described in WS-Security 1.0 [WSS10] and WS-Security 1.1 [WSS11] token profiles.

Actual messages that have been documented in WS-Security TC and other WS-Security-based Interops that conform to some of the example policies are referenced when appropriate.

The purpose of this document is to give examples of how policies may be defined for several existing use cases that have been part of the WS-Security Interops that have been conducted. In addition, some example use cases have been included which show some variations from the WS-Security Interop use cases in order to demonstrate how different options and security bindings impact the structure of the policies.
Group OASIS Web Services Secure Exchange (WS-SX) TC
Folder Examples
Submitter Rich Levinson
Date Submitted Tuesday, 11 May 2010 08:44pm
Document State Draft (A preliminary unapproved sketch, outline, or version.)
Access This document is visible to OASIS Web Services Secure Exchange (WS-SX) TC and shared with:
  • OASIS Open (General Membership)
  • General Public

Subject & Text Submitter Date Action
Initial comment by submitter
This document has followed the procedure directed by TC-Admin:
1. Download CS01 doc file
2. Make the following changes:
a: Change stage to Committee Draft 02
b: Change date to 3 February 2010
c.: Copy the 'this version' URIs to the 'previous version' section. Make sure that the actual hypertext links match the text string.
d.: Edit the 'this version' URIs by replacing 'cs-01' with 'cd-02'. Make sure that the actual hypertext links match the text string.
e. Update the running footer with the updated filename (minus extension) and date.
f. Update the acknowledgements and references.
3. Create the PDF and HTML versions.
4. Zip it all up.
5. Send it to TC-Admin

This was the version that was the basis of the vote that did not pass because all voting members were not aware that the ballot was outstanding, although notifications were sent for the ballot. Therefore we would like to resubmit the doc for another vote with all members prepared to vote.
Rich Levinson