Unfortunately no, I'm not an owner of Web service, I tried to force owner to use 1.5 but without success (they cannot change rampart version).
Regards Tom -----Original Message----- From: Prabath Siriwardana [mailto:[email protected]] Sent: Monday, October 11, 2010 4:52 PM To: [email protected] Subject: Re: WCF interoperatibility AXIS: signature or decryption was invalid Can you please test the same with Rampart 1.5... Thanks & regards, -Prabath On Mon, Oct 11, 2010 at 7:56 PM, Tomasz Sienkiewicz <[email protected]> wrote: > Hello, > > First of All I would like to say hello. > > I'm trying to create a WCF Client (.net 3.5) that will consume AXIS/Rampart > based WS. > Scenario: > WS: > - AXIS2 1.5.1 > - Rampart 1.4. > Security: > - WS uses HTTPS as transport protocol. > - WS uses X509 Digital Signature. > - WS uses UsernameToken. > Please find attached valid message, created in SOAP-UI > (SOAP-UI-VALID_REQUEST.xml). > > Client: > - WCF .NET3.5 > The message that is created by WCF is very similar to the SOAP-UI message > (WCF_INVALID_REQUEST.xml)- but I always get WS Exception > > 08 Oct 2010 13:52:15 ERROR (http-8080-1) org.apache.axis2.engine.AxisEngine > - WSDoAllReceiver: security processing failed > org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed > at > org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java > :214) > at > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.ja > va:86) > at > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) > at org.apache.axis2.engine.Phase.invoke(Phase.java:318) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HT > TPTransportUtils.java:167) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application > FilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh > ain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja > va:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja > va:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127 > ) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102 > ) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java > :109) > at > org.apache.catalina.ha.tcp.ReplicationValve.invoke(ReplicationValve.java:347 > ) > at > org.apache.catalina.ha.session.JvmRouteBinderValve.invoke(JvmRouteBinderValv > e.java:227) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http > 11Protocol.java:588) > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) > at java.lang.Thread.run(Thread.java:619) > Caused by: org.apache.ws.security.WSSecurityException: The signature or > decryption was invalid > at > org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(Signa > tureProcessor.java:529) > at > org.apache.ws.security.processor.SignatureProcessor.handleToken(SignaturePro > cessor.java:97) > at > org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngi > ne.java:326) > at > org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngi > ne.java:243) > at > org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java > :211) > ... 23 more > > Please find attached logs from AXIS. > - WCF-REQUEST_SERVERSIDE_LOG.TXT - log from axis for invalid WCF message > - WCF-REQUEST_CLIENTSIDE_FIDDLER.txt- invalid message captured using fiddler > - SOAP_UI_REQUEST_SERVERSIDE_LOG- log from axis for valid SOAP message > created in SOAP-UI > - SOAP_UI_REQUEST_CLIENTSIDE_FIDDLER_LOG.txt- valid SOAP message taken from > SOAP-UI request editor. > > Could you help me fix it? > > Regards > Tom > -- Thanks & Regards, Prabath Siriwardena http://blog.facilelogin.com http://RampartFAQ.com
