Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I had to do a lot of reading between multiple articles to get the details I was looking for from my original post. The information that helped things to clear up a bit for me was the following:</p> <p><em>Each protocol (TCP, HTTP, MSMQ, NamedPipes) has its own mechanism for passing credentials and handling message protection.</em></p> <p>Above is from the <a href="http://wcfsecurityguide.codeplex.com/releases/view/15892" rel="noreferrer">WCFSecurityGuide</a></p> <p>Coming from a primarily web background I have a pretty good understanding of HTTP and securing it with a SSL cert. However this exact procedure is not required in a Windows environment for net.tcp which uses its own method in Windows to secure the transport layer. </p> <p>So when it gets down to it, here are the (2) explinations in regards to securing a HTTP binding and net.tcp in a Windows environment that I wanted to understand:</p> <p><strong>For net.tcp:</strong> <em>The service and clients are authenticated using Windows authentication, and the messages are secured at the transport level by Windows security</em></p> <p><strong>For a HTTP binding (i.e. wsHttpBinding):</strong> <em>When using HTTP bindings, the transport security is provided by SSL. The SSL certificate is used to provide the message protection.</em></p> <p>So I will <em>not</em> need a SSL cert for the net.tcp binding as that is handled by Windows Security and is inheriently secure when using Transport security. When using a wsHttpBinding I will still need to secure the Transport with a SSL certificate which I had done as mentioned previously, and exposed the binding via HTTPS.</p> <p>If any future readers have similar questions the WCF guide link I posted and the link below are a good place to start:</p> <p><strong>Common WCF Security Scenarios:</strong><BR> <a href="http://msdn.microsoft.com/en-us/library/ms730301.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/ms730301.aspx</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload