The Secure Sockets Layer (SSL) / Transport Layer Security (TLS) protocol is used to encrypt Internet communication. This is important for protecting the privacy of your users and for safekeeping sensitive information that is being sent. If you do not protect the sensitive information on your website, you can become susceptible to man-in-the-middle attacks. Such attacks happen when the attacker intercepts communication between two systems (e.g., a server and a client web browser). The attacker can eavesdrop on messages being sent and also possibly alter them without being detected.
How to start using SSL on your website
What are SSL certificates
SSL certificates are electronic documents, which use a digital signature to bind a public key (needed to establish a secure connection) with a server. The digital signature is provided either by the certificate itself (a self-signed certificate) or by a Certificate Authority:
- You can create them easily by yourself, but they are less secure than those signed by a Certificate Authority.
- Great for testing servers and suitable for collecting personal (non-financial) information.
- You should not use a self-signed certificate on an e-commerce site.
Certificates signed by a Certificate Authority
- Must be issued by a Certificate Authority, which verifies that the subject (server) of the certificate is what it claims to be.
- Can be expensive, but provide high security.
- It is generally recommended to use this type of certificate.
When should you use the SSL protocol
Using TLS / SSL (HTTPS protocol) is recommended for most websites. Particularly if you transmit any sensitive data, including the following use cases:
- Your website contains sign-in forms.
- Your website transmits personal information (e.g., social security numbers) and otherwise sensitive information (e.g., emails).
- Your website collects and transmits credit card information (to prevent man-in-the-middle attacks).
Creating a self-signed certificate in IIS
Open IIS Manager.
Click on the name of your server in the Connections column on the left.
Double-click the Server certificates.
In the Actions pane, click Create Self-Signed Certificate.
Type a friendly name for the certificate in the Specify a friendly name for the certificate box, and click OK.
The IIS server creates a new self-signed certificate with the name of your server as its common name.
Binding a certificate to a website
If you already have an SSL certificate (self-signed or from a Certificate authority), you need to configure the IIS server so that it can use it for incoming secure connections.
When using the MVC development model, you need to configure SSL (HTTPS) separately for both your live site and the Kentico administration application.
- Open IIS Manager.
- Select a website, you want to bind the certificate to, in the Connections column on the left.
- Click Bindings... in the Actions column.
- Click Add...
- Change the Type to https.
- Select the certificate from the list.
- Click OK and close the Site bindings dialog.
The IIS server is now ready for using the assigned certificate with SSL handshake for incoming connections.
Securing the administration interface
You can configure the Kentico administration interface to only be accessible through the HTTPs protocol.
- Open the Settings application.
- Navigate to the Security & Membership category.
- In the Administration category, select the Use SSL for administration interface field.
- Click Save.
Now all editors and administrators will be redirected to UI pages using the https URL scheme when they sign in to the administration interface.
This setting applies to all sites in the system. It is available only if you select the (global) option from the Site drop-down list.
Configuring pages to use HTTPS
Securing MVC sites
For sites built using the MVC development model, developers can ensure that pages are only accessible over a secured protocol (HTTPS) by using the RequireHttpsAttribute. You can either secure individual controllers or register the attribute as a global filter for the entire website.
Securing Portal Engine sites
For Portal Engine sites, Kentico allows you to specify which of the pages are accessible over a secured protocol (HTTPS). When users try to open such a page with the standard HTTP protocol, they will be automatically redirected to the secured version of the same page (using the https URL scheme).
When you set up a page to require SSL access, the system only redirects HTTP requests to the secure HTTPS protocol. Kentico does not configure the website to use the HTTPS protocol. You still need to adjust your IIS settings to use SSL/HTTPS.
- Open the Pages application.
- Select a page in the content tree.
- Open the Properties -> Security tab.
- In the Access section switch Requires SSL to Yes (or Inherits to load the value from the parent page).
- Click Save.
Now all users attempting to access the page will always be redirected to the HTTPS version of the page's URL.
Was this page helpful?