Re: Problems with the SOAP binding

The "wrapper" proposals for refPs would not allow this "problem" to occur.

It seems the "feature" of top level refPs as headers is full of problems.

The "wrapped" wss:RefPRops or wsa:To headers could be read by 
intermediaries,
they just would not be top level headers.  

Tom Rutt
Fujitsu

Rich Salz wrote:

>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$
>  
>

-- 
----------------------------------------------------
Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133