What does "#_1" refer to in the original request - the wsa:To header? CXF is not signing that in the example request and this is probably why security is failing. Is CXF including the wsa:To header in the request?
Colm. On Fri, May 4, 2012 at 1:51 PM, gmui <[email protected]> wrote: > Hi Daniel, > Thanks for the reply. I have been following what you suggested in terms of > allowing CXF to respond based on the WS-SecurityPolicy that is provided as > part of the WSDL. After getting all the jar dependencies and properties and > certificates set up, I am able to get the SOAP request to go out to the web > service but am getting the following error: > > > > *Here is the WS-Policy from the wsdl:* > > > > *Here is the security entry for a working request:* > > > > > *And here is an entry for my CXF request which fails:* > > > Any suggestions on how I can diagnose and resolve? This is a "standard" > wsHttpBinding configuration (using Transport security w/o client certificate > and Message security with client certificate security). I haven't found any > posts that suggest anybody else has gotten this to work so figuring this out > would be a great step towards .NET / CXF interop. > > Thanks, > Gary > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/More-cxf-wcf-interop-questions-tp5681573p5685781.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
