cancel
Showing results for 
Search instead for 
Did you mean: 

WS-RM and WS-Security Together

Highlighted
Not applicable

WS-RM and WS-Security Together

Hello,

I am trying to use soapUI 4.0.1 to call a JAX-WS web service that has a policy set that includes both WS-Security and WS-RM (and WS-Addressing). The reliable messaging requests being created do not contain the required UserNameToken header elements, and it's causing my requests to fail. If I remove WS-RM from the request, it sends the single request with the security header as expected.

Is this a supported configuration, or perhaps I'm not setting something in the client correctly? Any help or suggestions are greatly appreciated.

Thanks in advance,
Tony
1 REPLY 1
Highlighted
New Member

Re: WS-RM and WS-Security Together

Hello,

 

six years no one replay. A have same problem, when enabling WS-RM the CreateSequence goes without any WS-Security:

 

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence</wsa:Action>
<wsa:MessageID>uuid:01bf364b-3100-40d5-a23f-fa0aadac06ef</wsa:MessageID>
<wsa:To>http://localhost/ZPMessageBoxGW/service.svc</wsa:To>
</soap:Header>
<soap:Body xmlns:wsrm="http://docs.oasis-open.org/ws-rx/wsrm/200702">
<wsrm:CreateSequence>
<wsrm:AcksTo xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous?id=cad573f2-11dd-4f35-9ac0-e28ca3040aad</wsa:Address>
</wsrm:AcksTo>
</wsrm:CreateSequence>
</soap:Body>
</soap:Envelope>

Jozef