Next in thread →
Next in month →
RE: [ws-sx] Issue ER020: An issue with ContentEncryptedElements
Title: An issue with ContentEncryptedElements I believe for section 8.1 of sp v1.2, the line should be 2227 rather than 2325. From: Marc Goodner [mailto:] Sent: Tuesday, September 15, 2009 9:23 AM To: Vladov, Stefan; Cc: Subject: [ws-sx] Issue ER020: An issue with ContentEncryptedElements Issue number ER020. From: Vladov, Stefan [mailto:] Sent: Wednesday, September 09, 2009 4:30 AM To: Subject: [ws-sx-comment] An issue with ContentEncryptedElements Hi guys, I'm resubmitting the problem with having a ContentEncryptedElements protection assertion inside a SupportingToken assertion as an issue and I propose the following resolution: Please change section 8.1 as below: a. Amend the Syntax (pseudo schema) as below: Syntax <sp:SupportingTokens xmlns:sp="..." ... > <wsp:Policy xmlns:wsp="..."> [Token Assertion]+ <sp:AlgorithmSuite ... > ... </sp:AlgorithmSuite> ? ( <sp:SignedParts ... > ... </sp:SignedParts> | <sp:SignedElements ... > ... </sp:SignedElements> | <sp:EncryptedParts ... > ... </sp:EncryptedParts> | <sp:EncryptedElements ... > ... </sp:EncryptedElements> | <sp:ContentEncryptedElements ... > ... </sp:ContentEncryptedElements> ) * ... </wsp:Policy> ... </sp:SupportingTokens> b. Add the following text at the end of section 8.1 (after line 2325): /sp:SupportingTokens/wsp:Policy/sp:ContentEncryptedElements This OPTIONAL element is a policy assertion that follows the schema outlined in Section 4.2.3 and describes additional message elements whose content MUST be encrypted using the token identified by this policy assertion. c. Please make changes similar to the above to sections 8.2, 8.3 and 8.4 I hope you approve the proposed change. Best regards, Stefan
Next in thread →
Next in month →