Securing sites is already a mandatory step in many businessas usually it is saving sensitive data and documents. Moreover, with cloudhosting, server capacity must be added and removed dynamically. Before WindowsServer 2012, there were a couple of obstacles must be considered :
And CCS is the Solution: The DNS name and CN name of thecertificate must match. This contract can be further extended to the file namesof the certificates. (For example, www.Server1.com would use the certificatewith a file name www. Server1.com.pfx.) This contract enables Windows Server2012 to have just one SSL binding, regardless of the number of secure sitesthat use CCS store for binding certificates.
Simply previously if there were 100 secure sites, there would 100 SSLbindings “Explicit Binding”. But with CCS regardless the number of secure sites, there would be single SSLbindings “Implicit Binding”.
How to configure it in IIS ?
How to configure website to use CCS?
When choose CCS then no need to select certificate … it just go and picked it up from the share but it must be certificate name like website name exactly
Where CCS is Configured ?
CCS configuration is stored in Registry and not in Application Host
IIS sslFlags is just to verify if website uses CCS.
<binding protocol="https" bindingInformation="*:443:CentralSSL0" sslFlags="3" />
Nice article. thanks!
P.S: There is a typo; And CSS is the Solution.
Thanks Reyou ... Corrected :)