[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-sx] Issue i142: Examples 2.2.3 and 2.2.4 are miss-labeled
Issue i142. > -----Original Message----- > From: Hal Lockhart [mailto:hlockhar@bea.com] > Sent: Monday, July 02, 2007 12:47 PM > To: ws-sx@lists.oasis-open.org > Cc: Marc Goodner > Subject: [ws-sx] New Issue: Examples 2.2.3 and 2.2.4 are miss-labeled > > PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL > THE ISSUE IS ASSIGNED A NUMBER. > The issues coordinators will notify the list when that has occurred. > > Protocol: ws-sp examples > > http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/24008/ws > -sp-usecases-examples-draft-14-02.doc > > > Artifact: examples > > Type: > > editorial > > Title: > > Examples 2.2.3 and 2.2.4 are miss-labeled > > Description: > > Examples 2.2.3 and 2.2.4 are identified as being based on WSS 1.1. > However, both require the use of mechanisms (e.g. DerivedKeyToken) > defined in WS-SecureConversation. > > The text refers to EncryptedKey as a WSS 1.1 feature, but EncryptedKey > is defined by XML Enc and has been present in WSS since version 1.0. I > am not sure if there is any dependency of these examples on WSS 1.1, but > surely their use of WS-SecureConversation is a much more significant > difference between them and the prior examples. > > Related issues: > > None > > Proposed Resolution: > > Modify the titles of these examples to make it clear that they are > examples of the use of WS-SecureConversation, not (just) WSS 1.1.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]