It is important to note that these certificates should only be used for development and testing purposes, since only your browser running on your local machine will know the certificate, and therefore will show warnings that the certificate is invalid.
Once you have configured and installed the SSL certificates, you can leverage these for SSL-based communication in the sites configured on your IIS. To do this you need to configure the protocol bindings for SSL, as well as the SSL options for any web apps within the web-sites.
Configuring Bindings for SSL in IIS
Bindings are used for making the content of websites available using specific protocols, IP addresses, and ports. In addition, the host headers for accessing multiple web apps through the same IP address and port are also configured in the bindings. To use SSL for apps configured within a website, you will need to configure a protocol binding for SSL for that website. To do this, select your website in the navigation tree of the IIS Management Console and then select the Bindings link from the right hand side task pane. A dialog will appear which allows you to configure the bindings. Here, you add the new bindings to make the contents available through different IP addresses, protocols, and ports as shown below. Click Add to add new a binding to the website, and Edit button to modify existing bindings in the list.
As you can see from the below screenshot, the protocol has been configured to https running on the default IP address for the server, and uses port 443 for SSL-based access (the default port for SSL). In addition, in the dropdown list you can select the certificate to be used for SSL traffic on the website. Each certificate which you installed previously is available for selection in this listing, and you can set up different certificates for different websites on the server. After you have configured the SSL binding for your website, you can enable SSL for web applications within the website.
Encoding Information with SSL
SSL is enabled and configured for each individual site/app in IIS. Once you have configured the bindings at the website level, you can select the web app of your choice in the nav tree of the IIS Management Console and then activate the SSL configuration as shown below:
You can specify the requirement for SSL encoding for the chosen web app and whether to require client certificates to authenticate users. If you are using client certificate authentication you will need to configure the certificate mappings from certificates to the users that are eventually authenticated by IIS when retrieving the certificate. Configure these mappings in the web.config file.