- From: Rich Salz <rsalz@datapower.com>
- Date: Tue, 21 Dec 2004 18:44:38 -0500 (EST)
- To: "Srinivas, Davanum M" <Davanum.Srinivas@ca.com>
- cc: "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>
Yes, if you relax the rules for opacity, and allow the client to do special processing when required, then the client can "merge" the two ws-security messages (one in the refp and one it generates). So yes, since the current SOAP binding is "broken," this change to the SOAP binding will address the issue. As I said on the call (and in email), I'd want Gudge's opinion. It'll be interesting to see how to violate opacity. :) /r$ -- Rich Salz Chief Security Architect DataPower Technology http://www.datapower.com XS40 XML Security Gateway http://www.datapower.com/products/xs40.html XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html
Received on Tuesday, 21 December 2004 23:44:41 UTC