[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue 106: Why does a <IssuedTokens> element contain an RSTRinstead of an RSTRC?
Issue 106 -----Original Message----- From: Hal Lockhart [mailto:hlockhar@bea.com] Sent: Tuesday, August 22, 2006 2:54 PM To: ws-sx@lists.oasis-open.org Cc: Marc Goodner Subject: New Issue: Why does a <IssuedTokens> element contain an RSTR instead of an RSTRC? 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 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: Why does a <IssuedTokens> element contain an RSTR instead of an RSTRC or a choice of RSTR or RSTRC? Description: Since a <IssuedTokens> element may need to contain Tokens issued as the result of multiple requests, why is it not allowed to contain a <RequestSecurityTokenResponseCollection> element? Related issues: Proposed Resolution: Option 1: Permit an <IssuedTokens> element to contain a choice of a <RequestSecurityTokenResponse> element or a <RequestSecurityTokenResponseCollection> element. Option 2: Change the <IssuedTokens> element to contain a <RequestSecurityTokenResponseCollection> element. Hal
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]