title: Using certificate only on server side
body: <p>I'm working on some WCF application. I already have client-side and server-side. Both communicates using WCF netTcpBinding or netNamedPipe. I want also a certificate only on server side, similar as it is with HTTPS. I've found very helpful guide here <a href="https://talkdotnet.wordpress.com/2014/03/20/wcf-security-cia-confidentiality-integrity-and-authentication-using-ssl-certificates/" rel="nofollow noreferrer">click</a>.</p>
  
  <p>So according to this article, I'm interested in option 1 which is </p>
  
  <blockquote>
    <p>Option one provides (C + I) no authentication will happen for the client, In this case the TCP SSL (not the HTTPS SSL) will be used to provide the Confidentiality and Integrity, and the service will be configured like this below.</p>
  </blockquote>
  
  <p>For now everything is clear for me, unfortunately later we can read: </p>
  
  <blockquote>
    <p>also you need to install the root certificate authority certificate for the service certificate on the client machine (typically in the Local Machine/Trusted Root Certification Authorities), and the service needs to have the below behaviour to specify the certificate for the service.</p>
  </blockquote>
  
  <p>So here comes my question, is there any way to avoid changes on client machine? As mentioned earlier, I'm looking for a solution similar to WEB where the user is not obligated to install any kind of certificate on his machine.</p>
  
  <p>Maybe I'm missing something, but maybe this rule applies only when I'm using a self-trusted/developer certificate? What if I will get certificate from a trusted company like Verisign?</p>