Re: Signature problem after migrating an Apache CXF client from 2.2.6 to 2.4.7 and the same microsoft server on the serverside: "The signature or decryption was invalid"

Colm, you saved my day! with setting "isBSPCompliant" to false... outProps.put(WSHandlerConstants.IS_BSP_COMPLIANT, Boolean.FALSE.toString()); ... the microsoft server can process my request. Thank you VERY VERY much! Best regards, Peti 2012/5/15 Colm O hEigeartaigh > What configuration are

Re: Signature problem after migrating an Apache CXF client from 2.2.6 to 2.4.7 and the same microsoft server on the serverside: "The signature or decryption was invalid"

What configuration are you using to generate the request? Try setting the following configuration property "isBSPCompliant" to "false" to see if it works - this will disable the InclusiveNamespaces stuff in CXF 2.4.7, in case this is causing the problem. Do you have access to more detailed loggin

Signature problem after migrating an Apache CXF client from 2.2.6 to 2.4.7 and the same microsoft server on the serverside: "The signature or decryption was invalid"

Hi all, We are using a generated Apache CXF client 2.2.6 with WSS4J 1.5.8 to send encrypted and signed payload to a web service. The old request looks like this: http://schemas.xmlsoap.org/soap/envelope/";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.