Hi,
Could you please append your testcase, both the working standalone cxf
client and the problem smx one?
If possible, also a standalone server what we can test against to
reproduce the error, I understand you are using .NET server on
windows, but if you can provide a cxf server to simulate the error it
would be great.
Thanks
Freeman
On 2009-8-12, at 下午11:14, XyLus wrote:
Hi All,
I have to connect to web service ( .NET implementation with WSE 3.0 on
board) that requires signed
request. I 've played with CXF framework and now I have solution
that works
just fine ( I get successful response from web service)
When I use cxf bc provider with the same configuration I end up with
'The
signature or decryption was invalid' error.
I attach smx and cxf logs and requests produced by CXF standalone
application and SMX flow.
http://www.nabble.com/file/p24938687/cxf.log cxf.log
http://www.nabble.com/file/p24938687/cxf.xml cxf.xml
http://www.nabble.com/file/p24938687/smx.log smx.log
http://www.nabble.com/file/p24938687/smx.xml smx.xml
When you compare them they look ALMOST the same what makes me
confused.
(digest value and signature value are different and one additional
namespace
is avaialbe in smx request
http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper)
So I turned on debug mode and tried to find root cause of differences.
However I can't see any meaningful information in logs . On top of
that I
use the same version of wss4j and xmlsec library in both cases.
Any help appreciated.
Regards,
Maciej
--
View this message in context:
http://www.nabble.com/Once-again%3A-Microsoft.Web.Services3.Security.SecurityFault%3A-The-signature-or-decryption-was-invalid-tp24938687p24938687.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
