Re: [wss] SOAP MustUnderstand issue

> I would expect that the intermediary add a new wsse:Security header with
> the mU attribute and all elements under the wsse:Security header use the
> semantics associated with the parent wsse:Security header by default.

It can't do that if both elements are targeted to the same recipient.
	/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