MTOM secure interop testscases fail throwing security verification excpetion

[glassfishrobot]

Happens on all secure MTOM testcases. Looks like MS is not able to consume our message.

Sample stack trace.

testEchoBinaryAsString Failed! javax.xml.ws.soap.SOAPFaultException: An error occurred when verifying security for the message. at com.sun.xml.wss.jaxws.impl.SecurityClientPipe.process(SecurityClientPipe.java:268) at com.sun.xml.ws.protocol.soap.ClientMUPipe.process(ClientMUPipe.java:58) at com.sun.xml.ws.handler.HandlerPipe.process(HandlerPipe.java:107) at com.sun.xml.ws.handler.HandlerPipe.process(HandlerPipe.java:107) at com.sun.xml.ws.client.Stub.process(Stub.java:121) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:122) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:238) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:212) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:105) at $Proxy36.echoBinaryAsString(Unknown Source) at mtom.soap11signonly.client.JAXWSClient.testEchoBinaryAsString(JAXWSClient.java:70) at mtom.soap11signonly.client.JAXWSClient.main(JAXWSClient.java:41) Aug 29, 2006 2:35:01 PM com.sun.xml.wss.impl.filter.DumpFilter process

Transport dump log is attached.

Environment

Operating System: All Platform: All

Affected Versions

[current]

[glassfishrobot]

Reported by vrdeepak@java.net

[glassfishrobot]

vrdeepak@java.net said: Created an attachment (id=9) Transport dump

[glassfishrobot]

tamiro@java.net said: Bugswat asked to upgrade to P2

[glassfishrobot]

tamiro@java.net said: Bugswat decided to waive this issue for Milesone 2.

[glassfishrobot]

jdg6688@java.net said: This was due to bug in WCF which was fixed.

[glassfishrobot]

vrdeepak@java.net said: This issue is fixed in WCF after Sept CTP. But WSIT M3 requires to interoperate with Sept CTP, hence re-opening the bug.

[glassfishrobot]

vrdeepak@java.net said: Adding more details. The following exception is thrown by the Indigo client side. 10 testcases are failing due to this.

======snip====== ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ServiceModel.Security.MessageSecurityException: Message security verification failed. ---> System.Security.Crypt ography.CryptographicException: Digest verification failed for Reference '#3'. at System.IdentityModel.Reference.EnsureDigestValidityIfIdMatches(String id, Object resolvedXmlSource) at System.IdentityModel.Reference.EnsureDigestValidity(String id, Object resolvedXmlSource) at System.ServiceModel.Security.WSSecurityOneDotZeroReceiveSecurityHeader.ValidateDigestsOfTargetsInSecuri tyHeader(StandardSignedInfo signedInfo, SecurityTimestamp timestamp, Boolean encryptedFormReaderRequired, Boolean isPrimarySi gnature, Object signatureTarget, String id) at System.ServiceModel.Security.WSSecurityOneDotZeroReceiveSecurityHeader.VerifySignature(SignedXml signed Xml, Boolean isPrimarySignature, SecurityHeaderTokenResolver resolver, Object signatureTarget, String id) at System.ServiceModel.Security.ReceiveSecurityHeader.ProcessPrimarySignature(SignedXml signedXml, Boolean isFromDecryptedSource) at System.ServiceModel.Security.ReceiveSecurityHeader.ExecuteSignatureEncryptionProcessingPass() at System.ServiceModel.Security.LaxModeSecurityHeaderElementInferenceEngine.ExecuteProcessingPasses(Receiv eSecurityHeader securityHeader, XmlDictionaryReader reader) at System.ServiceModel.Security.ReceiveSecurityHeader.Process(TimeSpan timeout) at System.ServiceModel.Security.MessageSecurityProtocol.ProcessSecurityHeader(ReceiveSecurityHeader securi tyHeader, Message& message, SecurityToken requiredSigningToken, TimeSpan timeout, SecurityProtocolCorrelationState[] correlat ionStates) at System.ServiceModel.Security.AsymmetricSecurityProtocol.VerifyIncomingMessageCore(Message& message, Str ing actor, TimeSpan timeout, SecurityProtocolCorrelationState[] correlationStates) at System.ServiceModel.Security.MessageSecurityProtocol.VerifyIncomingMessage(Message& message, TimeSpan t imeout, SecurityProtocolCorrelationState[] correlationStates) — End of inner exception stack trace —

Server stack trace: at System.ServiceModel.Security.MessageSecurityProtocol.VerifyIncomingMessage(Message& message, TimeSpan t imeout, SecurityProtocolCorrelationState[] correlationStates) at System.ServiceModel.Channels.SecurityChannelFactory1.SecurityRequestChannel.ProcessReply(Message reply , SecurityProtocolCorrelationState correlationState, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory1.SecurityRequestChannel.Request(Message message, T imeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime o peration, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime o peration, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOper ationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at IMtomTest.EchoStringAsBinary(String s) at MtomTestClient.EchoStringAsBinary(String s) — End of inner exception stack trace — at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, M ethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAtt ributes methodAttributes, RuntimeTypeHandle typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, O bject[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) at Microsoft.Xws.Test.Suite.Util.WsdlTestUtilities.DynamicProxy.DynamicObject.CallMethod(String method, Ob ject[] parameters) at XwsInterop.HostedClient.HostedClientSoapImpl.TestMtomMethods(DynamicProxy proxy, Boolean enableSecurity , String operationName) at XwsInterop.HostedClient.HostedClientSoapImpl.runScenario(String featureName, String scenarioName, Hoste dClientParameter[] parameters) ======snip======

[glassfishrobot]

kumarjayanti@java.net said: Waived for WSIT M3.

Need To Check if it passes with RTM of WCF eventually.

Actually it is already passing with WCF RTM Today.

[glassfishrobot]

venu@java.net said: Harsha checked with latest jaxws build. This scenario is working. Looks like jaxws rt is not integrated into m3.

[glassfishrobot]

venu@java.net said: please ignore my prev comment

[glassfishrobot]

kumarjayanti@java.net said: Closing the task since Secure MTOM Interop scenarios have been verified with WCF RTM.

[glassfishrobot]

mmatula@java.net said: This issue was fixed before we created 1.0 branch, so the fix is in 1.0 -> setting target milestone to say so.

[glassfishrobot]

File: msglog.txt Attached By: vrdeepak@java.net

[glassfishrobot]

Was assigned to ashutoshshahi@java.net

[glassfishrobot]

This issue was imported from java.net JIRA WSIT-59

[glassfishrobot]

Marked as fixed on Tuesday, July 22nd 2008, 10:44:57 am