We have our own certificate, which we use as part of ClientCredentials in the transport client credentials, as shown below.
WSHttpBinding wsBinding = new WSHttpBinding(); wsBinding.Security.Mode = System.ServiceModel.SecurityMode.Transport; wsBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate; wsClient = new WSService.WSClient(wsBinding, new EndpointAddress(serviceURL)); wsClient.ClientCredentials.ClientCertificate.SetCertificate(StoreLocation.LocalMachine, StoreName.My, X509FindType.FindBySubjectName, clientCertificateSubjectName);
Our partner also provided us with a copy of his certificate, which is used on the server to verify their server. Calls to the service are currently doing well unless we have installed or done anything with this certificate.
We use ColdFusion, and as a rule, we should install them in the java certificate store, but it seems strange to me that the service connection works in Visual Studio when I did nothing with the service certificate
What is the role / purpose of the service certificate? Clients install it in trustees of MMC certificates or refer to it in the client configuration, for example. WSHttpBinding above?
source share