[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New Issue: The <IssuedTokens> Element is not used by WS-SC
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-trust / ws-sc http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/18840/ws -secureconversation-1.3-spec-ed-01-r06-diff.pdf http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/18833/ws -trust-1%5B1%5D.3-spec-ed-01-r08-diff.pdf Artifact: spec / schema? Type: design Title: WS-Trust (section 4.4) defines a <wst:IssuedTokens> element to be used to contain tokens referenced by an RST or RSTR and also some other protocol. I am not entirely convinced that this is all that useful, but I notice that it is NOT used by WS-SecureConversation. It seems like it should be or should be dropped from WS-Trust. Description: Presumably having a top level SOAP header element to contain tokens make it easier to find them. It is not clear this has any benefit over putting then in the <wsse:Security> element. However, if it is a good idea, the WS-SC should use it as well. If it is used, the MustUnderstand semantics of it should be described as it is a top level element in the SOAP header. Related issues: Issue #78 Proposed Resolution: a) Drop <wst:IssuedTokens> from WS-Trust. b) Add <wst:IssuedTokens> to WS-SC. Provide Rationale. Describe MustUnderstand semantics in both specs. Hal
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]