Ok thanks - it's the same error in both. Do you have access to debug logging on the service provider side? It's hard to tell what's going wrong the digest of the SOAP Body, without being able to compare the canonicalized version of it on both sides.
You mentioned that there is no signature validation error when the request is correct. Is the response Body also signed and encrypted in this case? Could you attach a log for that as well so that I can compare? Finally, could you try changing the security policy so that the SOAP Body is not encrypted, only signed, and see if that works. Colm. On Wed, May 23, 2012 at 11:25 AM, Yuriy Flyud <[email protected]> wrote: > CXF 2.6.0 FINE log: > http://cxf.547215.n5.nabble.com/file/n5708372/log.log log.log > > Take a look at last exception: > /Exception in thread "main" java.lang.NullPointerException/ > This was fixed in 2.6.1-SNAPSHOT. Here is corresponding thread: > http://cxf.547215.n5.nabble.com/How-to-resolve-PolicyReference-using-Dispatch-API-td5651158.html > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Error-message-from-server-cannot-be-decrypted-tp5708282p5708372.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
