title: SSL Error with WCF Service using Transport Security & Cert. Authentication
body: <p>I don't know if this is a question more suited for Serverfault.com, really depends on the answer, but I have followed <a href="http://msdn.microsoft.com/en-us/library/cc949005.aspx" rel="nofollow noreferrer">this tutorial</a> in .NET C# to setup a WCF service under 'wsHttpBinding' (Transport Security &amp; Certificate Authentication), I have created a test development certificate using the methods described <a href="http://msdn.microsoft.com/en-us/library/cc949067.aspx" rel="nofollow noreferrer">here</a> and I have also configured my HTTPS 443 port in Bindings for IIS.</p>
  
  <p>Everything has been working pretty good each step, however I am receiving an error in the the Example "Hello World" service I created (again, all followed via the MSDN tutorial link I first stated) when hitting <code>https://vd1/WcfWsHttpBindingTest/Service.svc</code> (VD1 being my local computer name):</p>
  
  <pre><code>HTTP Error 403.7 - Forbidden
  The page you are attempting to access requires your browser to have a Secure Sockets Layer (SSL) client certificate that the Web server recognizes.
  </code></pre>
  
  <p>I have followed both tutorials as stated to install my <a href="http://msdn.microsoft.com/en-us/library/cc949067.aspx" rel="nofollow noreferrer">server certificate</a> and the <a href="http://msdn.microsoft.com/en-us/library/cc949057.aspx" rel="nofollow noreferrer">client certificate</a> and it has been configured in IIS; Also if I negate the 'https' and just use 'http' I receive a 403.4 Forbidden stating I am trying to access a page which has been secured with SSL, so I'm pretty sure that side of it is working.</p>
  
  <p>Any ideas folks?<br />
  I haven't deviated from the tutorials, I am running IIS 7.0 and Vista Business.</p>
  
  <p>It would even help if somebody could start me from a clean slate by giving me better tutorial links for configuring a service with wsHttpBinding.</p>
  
  <p>** <strong>If anyone had seen my initial post, you will notice I closed my answer as it has evolved to the problem above</strong> **</p>