So with a .NET client to CXF service it works fine, but not with a CXF client to CXF service? Could you attach the failing stacktrace, and also a message that the .NET client sends and a message the CXF client sends?
Colm. On Tue, Jun 26, 2012 at 11:00 PM, DTaylor <[email protected]> wrote: > Good day all, > > We finally have interop working with .NET and CXF. We need to be able to > encrypt our signature due to program requirements, but when we use the > attached WSDL, we get the error "The signature is not protected." and the > service faults out. With a .NET client, the attached WSDL works correctly. > > I have also attached our client configuration. > Any advice would be appreciated. > > Thanks, > > Dan. > > http://cxf.547215.n5.nabble.com/file/n5710349/TheSignatureIsNotProtected.wsdl > TheSignatureIsNotProtected.wsdl > http://cxf.547215.n5.nabble.com/file/n5710349/clientConfig.xml > clientConfig.xml > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/The-signature-is-not-protected-tp5710349.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
