Hi Jeff
AFAIK WS-Security requires WS-Addressing.. so if Amazon requires the
ReplyTo header, why not first add is with the Header mediator before the
send mediator is called?
<header name="To" value="http://www.w3.org/2005/08/addressing/anonymous"/>
asankha
Jeff Davis wrote:
Hi Everyone,
I have an interesting problem. I'm trying to setup Synapse so that I can use
to add the appropriate WS-Security stuff to outbound requests going to
Amazon's services such as SimpleDB (most of their services accept SOAP with
WS-Security). I'm able to properly configure the policy file so that the
BinarySecurityToken is added to the outbound request. Problem I have now is
that WS-Security also adds a few WS-Addressing elements automatically (even
when enableAddressing is not specified). For example, it adds:
<wsa:To>http://localhost:8086</wsa:To>
<wsa:MessageID>urn:uuid:CAB4C2774609414B961212810086922918001272489401</wsa:MessageID>
<wsa:Action>CreateDomain</wsa:Action
This is a problem insofar as Amazon then returns a message: "WS-Addressing
is missing a required parameter (ReplyTo)". Amazon does not require
WS-Addressing support, and when I remove those elements manually through
somethign like soapUI, I do get beyond this issue.
Any suggestions how I can get those WS-Addressing elements easily removed?
I'm wondering if I can put it through another sequence to remove it? I see
you can do some meta-data WS-Addressing stuff in WS-Policy, but I didn't see
a way of turning it off.
Thanks,
jeff
