无法调用简单的肥皂服务？

Question

I have tried everything before asking. I have a very simple service with url https://something . I can get WSDL using https://something?wsdl . Now I added reference this with Service Reference as well as Web Reference. But when I call it no SOAP header is sent(checked with Fiddler). I can call it with SOAP UI with no error. (BTW server is using WS-Security). Here is glimpse of SOAP UI request,

    <soapenv:Envelope xmlns:ns=""http://www.customs.pcfc.com/Schema/Declaration/TraderInboundServiceParameters/1.0"" xmlns:ns1=""http://www.customs.pcfc.com/Schema/Common/2.0"" xmlns:sad=""http://www.customs.pcfc.com/Schema/Declaration/SAD"" xmlns:soapenv=""http://schemas.xmlsoap.org/soap/envelope/"">
       <soapenv:Header>
    <wsse:Security soapenv:mustUnderstand=""1"" xmlns:wsse=""http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd""><wsse:BinarySecurityToken EncodingType=""http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"" ValueType=""http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"" wsu:Id=""CertId-1270251257"" xmlns:wsu=""http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"">xxx</wsse:BinarySecurityToken><ds:Signature Id=""Signature-847101547"" xmlns:ds=""http://www.w3.org/2000/09/xmldsig#"">
    <ds:SignedInfo>

    <ds:CanonicalizationMethod Algorithm=""http://www.w3.org/2001/10/xml-exc-c14n#""/>
    <ds:SignatureMethod Algorithm=""http://www.w3.org/2000/09/xmldsig#rsa-sha1""/>
    <ds:Reference URI=""#id-2038872614"">
    <ds:Transforms>
    <ds:Transform Algorithm=""http://www.w3.org/2001/10/xml-exc-c14n#""/>
    </ds:Transforms>
    <ds:DigestMethod Algorithm=""http://www.w3.org/2000/09/xmldsig#sha1""/>
    <ds:DigestValue>xx</ds:DigestValue>
    </ds:Reference>
    </ds:SignedInfo>
    <ds:SignatureValue>
   xxx
    </ds:SignatureValue>
    <ds:KeyInfo Id=""KeyId-1608734597"">
    <wsse:SecurityTokenReference wsu:Id=""STRId-161586721"" xmlns:wsu=""http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd""><wsse:Reference URI=""#CertId-1270251257"" ValueType=""http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3""/></wsse:SecurityTokenReference>
    </ds:KeyInfo>
    </ds:Signature></wsse:Security></soapenv:Header>
       <soapenv:Body wsu:Id=""id-2038872614"" xmlns:wsu=""http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"">
Body
    </soapenv:Body>
    </soapenv:Envelope>

Body is XML as well. Now I have tried this,

        var client = new WebServiceClient();
        var reader = new XmlSerializer(typeof(Request));
        var file = new StreamReader("a.xml");
        var fileData = (DeclarationRequest)reader.Deserialize(file);
        var cert = new X509Certificate2("Mycert.cer", "Pass");
        client.ClientCertificates.Add(cert);
        fileData.UNB.DateTime = DateTime.UtcNow;
        var b = client.process(fileData);

I am getting Invalid Certificate .

Then I tried Service Reference,

        var client = new MyClient();
        client.ClientCredentials.ClientCertificate.SetCertificate(StoreLocation.CurrentUser, StoreName.TrustedPublisher, X509FindType.FindByIssuerName, "Iss Name");
        var reader = new XmlSerializer(typeof(Request));
        var file = new StreamReader("a.xml");
        var fileData = (Request)reader.Deserialize(file);
        var request = fileData;
        request.UNB.DateTime = DateTime.UtcNow;
        ((BasicHttpBinding)client.Endpoint.Binding).Security.Mode = BasicHttpSecurityMode.Transport;
        ((BasicHttpBinding)client.Endpoint.Binding).Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;

        var response = client.process(request);

Here I am getting( Invalid Certificate again ),

The content type application/soap+xml; charset=UTF-8;action="process" of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 695 bytes of the response were:

'<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Header>
   </env:Header>
   <env:Body>
      <env:Fault><env:Code>
            <env:Value>env:Receiver
            </env:Value>
            <env:Subcode>
               <env:Value xmlns:fault="http://tempuri.org/soapfaults">fault:MessageBlocked
               </env:Value>
            </env:Subcode>
         </env:Code><env:Reason>
            <env:Text xml:lang="en">Invalid Certificate
            </env:Text>
         </env:Reason><env:Detail xmlns:fault="http://tempuri.org/soapfaults" fault:type="faultDetails">
         </env:Detail>



      </env:Fault>
   </env:Body>
</env:Envelope>'.

Answer 1

I fix it by following http://webservices20.blogspot.ae/2012/06/12-common-wcf-interop-confusions.html

In short I have,

[ServiceContractAttribute(ConfigurationName="ServiceSoap",ProtectionLevel=ProtectionLevel.Sign)]

    <bindings>
        <customBinding>
            <binding name="BPELProcess1Binding">
                <security authenticationMode="MutualCertificate" enableUnsecuredResponse="true" 
       messageSecurityVersion="WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10" />
                <textMessageEncoding messageVersion="Soap11" />
                <httpsTransport />
            </binding>
        </customBinding>
    </bindings>

    <behaviors>
        <endpointBehaviors>
            <behavior name="secureBehaviour">
                <clientCredentials>
                    <serviceCertificate>
                        <defaultCertificate findValue="My CA" storeLocation="CurrentUser" storeName="TrustedPublisher" x509FindType="FindByIssuerName" />
                    </serviceCertificate>
                </clientCredentials>
            </behavior>
        </endpointBehaviors>

    <client>
        <endpoint address="MyUrl" binding="customBinding" bindingConfiguration="BPELProcess1Binding" contract="MyContract" name="DeclarationB2BProcessing" behaviorConfiguration="secureBehaviour">
            <identity>
                <dns value="MyCertProp" />
            </identity>
        </endpoint>
    </client>