Hi Guys, I am trying to connect to a .NET service using Apache Axis 1.4 and WS-Security.
I am using wss4J version 1.5.1 and an addressing-SNAPSHOT.jar from Sandesha 1.0 The SOAP request contains the WS-Addressing elements and everything looks correct, it compares well with a sample SOAP request supplied by the customer. The only major difference is that the Apace UUID'd are different in format/style to the .NET clients. Q1. Does Apache Axis 1.4 work with .NET WSE 2.0 ? =========================================================================== <deployment name="defaultClientConfig" xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"> <globalConfiguration> <parameter name="disablePrettyXML" value="true"/> <parameter name="enableNamespacePrefixOptimization" value="false"/> <parameter name="addressing.sendReplyTo" value="true"/> </globalConfiguration> <service name="XXXX"> <requestFlow> <handler type="java:org.apache.axis.message.addressing.handler.AddressingHandler"> <parameter name="referencePropertyNames" value="{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}Action;{El ement}{http://schemas.xmlsoap.org/ws/2004/03/addressing}MessageID;{Element}{ http://schemas.xmlsoap.org/ws/2004/03/addressing}ReplyTo{Element};{http://sc hemas.xmlsoap.org/ws/2004/03/addressing}To"/> </handler> <handler type="java:org.apache.ws.axis.security.WSDoAllSender"> <!-- action order is important, do Timestamp then Signature if signing Timestamp --> <parameter name="action" value="Timestamp Signature"/> <parameter name="user" value="myuser"/> <parameter name="passwordCallbackClass" value="com.acme.security.PasswordCallback"/> <parameter name="signatureKeyIdentifier" value="DirectReference"/> <parameter name="signaturePropFile" value="pki/security.properties"/> <parameter name="timeToLive" value="300"/> <parameter name="precisionInMilliseconds" value="false" /> <parameter name="signatureParts" value="{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}Action;{El ement}{http://schemas.xmlsoap.org/ws/2004/03/addressing}MessageID;{Element}{ http://schemas.xmlsoap.org/ws/2004/03/addressing}ReplyTo;{Element}{http://sc hemas.xmlsoap.org/ws/2004/03/addressing}To;{Element}{http://docs.oasis-open. org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp;{Eleme nt}{http://schemas.xmlsoap.org/soap/envelope/}Body"/> </handler> </requestFlow> </service> </deployment> ============================================================================ ========= SOAP fault string : Microsoft.Web.Services2.Policy.PolicyVerificationException: WSE402: The message does not conform to the policy it was mapped to. at Microsoft.Web.Services2.Policy.SimplePolicyVerifier.VerifyMessageWithExpress ion(PolicyExpression expression, SoapEnvelope message, EndpointReference endpoint, String action, Uri requestEndpoint) at Microsoft.Web.Services2.Policy.SimplePolicyVerifier.Verify(SoapEnvelope message) at Microsoft.Web.Services2.Policy.PolicyVerificationInputFilter.ProcessMessage( SoapEnvelope envelope) at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope) at Microsoft.Web.Services2.Messaging.SoapReceiver.FilterMessage(SoapEnvelope envelope) at Microsoft.Web.Services2.Messaging.SoapReceiver.ProcessMessage(SoapEnvelope message) ============================================================================ ========= regards > Alick Buckley > > LANSA Research and Development > LANSA Pty Ltd > > Phone: +61289070243 > > http://www.lansa.com > mailto:[EMAIL PROTECTED] > > > >