Ok thanks. I've merged a fix for this which will appear in CXF 2.7.9.
Colm.
On Mon, Jan 20, 2014 at 1:56 PM, Kai Rommel wrote:
> Hi Colm, this is the complete policy
>
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> "
> xmlns:wsp="http://ww
Hi Colm, this is the complete policy
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
"
xmlns:wsp="http://www.w3.org/ns/ws-policy";>
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/Include
It sounds like a bug. What does your complete security policy look like?
Colm.
On Mon, Jan 20, 2014 at 1:42 PM, Kai Rommel wrote:
> Hi,
>
> I setup a request/response scenario with wss. The policy for the initiator
> token is set to /AlwaysToRecipient and for the recipient token to /Never.
> Si
Hi,
I setup a request/response scenario with wss. The policy for the initiator
token is set to /AlwaysToRecipient and for the recipient token to /Never.
Signature and encryption is configured.
The message exchange works fine and the request message looks like expected.
But the response message al
