ASP. NET Web configuration using HTTPS utility case

Step by step Configuring an ASP. NET Web application using HTTPS

For information on how HTTPS, SSL, and SSL certificates work, see

HTTPS (i) the HTTPS principle

"HTTPS those Things (ii) SSL Certificate"

HTTPS those things (iii) attack instances and defenses

This article demonstrates how to configure an HTTPS ASP. NET WEB application in IIS.

(1) Open Internet Information Services (IIS) Manager

(2) Create a self-signed Certificate

A self-signed certificate is an identity certificate the is signed by its own creator. Certificates is signed by Certificate authority. In general self signed certificates is fine for testing purpose and not for production.

There are two ways of creating self-signed certificate:

• Using IIS
• Tools for using Visual Studio MakeCert.exe

This article demonstrates only how to create self-signed certificate with IIS.

After you open IIS Manager, double-click Server certificates.

(3) Add a website to IIS

under Binding type Select HTTPS, the default port is 443 (HTTP default port is a), SSL certificate Select the self-signed certificate we created above.

(4) can also be used to add site binding method to implement

Click Add

(5) Open Browser

Click the small lock next to the address bar to view the certificate

(6) Open the Certificate Management tool to view trusted Root certification authorities

You can see that when you create self-signed certificate in IIS, the server has added it to the trusted Root ca. On the client side, you need to install the root certificate manually.

(7) Certification Authority

If you want to use a certificate that your browser trusts, you need to use a certificate issued to you by a certification authority (CA), such as Verisign,thawte. The self-signed certificate can be used to develop a test environment and should not be used in production environments.

Original link: http://www.cnblogs.com/jfzhu/p/4064654.html

ASP. NET Web configuration using HTTPS utility case