---
title: Configuring SSL
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

The Secure Sockets Layer 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 a communication between two systems (e.g., a server and a client web browser). The attacker can eavesdrop messages being sent and also possibly alter them without being detected.

## How to start using SSL on your website

1. Obtain a certificate from a certificate authority or [create a self-signed certificate](#creating-a-self-signed-certificate-in-iis).
2. [Bind the certificate to your website through IIS server](#binding-a-certificate-to-a-website).
3. [Configure pages in Kentico to redirect users to secured URLs](#configuring-pages-in-kentico-to-use-https).

## 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:

**Self-signed certificates**

- 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 who he 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

In general, every time you transmit any sensitive data. This includes cases:

- When your website contains login forms.
- When your website transmits personal information (e.g., social security numbers) and otherwise sensitive information (e.g., e-mails).
- Especially when your website collects and transmits credit card information (to prevent man-in-the-middle attacks).

You do not need SSL if your website only forwards users to third party payment processors (like PayPal) for entering credit card information. However, you have to make sure that users do not enter credit card information on your site.

## Creating a self-signed certificate in IIS

1. Open IIS Manager.
2. Click on the name of your server in the **Connections** column on the left.
3. Double-click the **Server certificates**.

   ![Click on the server name and open Server certificates](https://docs.kentico.com/docsassets/k10/configuring-ssl/IIS_server_certificates.png "Click on the server name and open Server certificates")
4. In the **Actions** pane, click **Create Self-Signed Certificate**.

   ![In the Actions pane, click Create Self-Signed Certificate](https://docs.kentico.com/docsassets/k10/configuring-ssl/IIS_create_certificate.png "In the Actions pane, click Create Self-Signed Certificate")
5. Type a friendly name for the certificate in the **Specify a friendly name for the certificate** box, and click **OK**.

   ![Type a friendly name for the certificate in the Specify a friendly name for the certificate box, and click OK](https://docs.kentico.com/docsassets/k10/configuring-ssl/Friendly_name.png "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.

1. Open IIS Manager.
2. Select a website, you want to bind the certificate to, in the **Connections** column on the left.
3. Click **Bindings...** in the **Actions** column.

   ![Select your website and click Bindings...](https://docs.kentico.com/docsassets/k10/configuring-ssl/IIS_bindings.png "Select your website and click Bindings...")
4. Click **Add...**
5. Change the Type to **https**.
6. Select the certificate from the list.

   ![Select the certificate from the list](https://docs.kentico.com/docsassets/k10/configuring-ssl/IIS_select_the_certificate.png "Select the certificate from the list")
7. 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.

## Configuring pages in Kentico to use HTTPS

Kentico allows you to specify which of the website's pages should only be 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).

> **Note:** 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.

### Securing individual web pages

1. Open the **Pages** application.
2. Select a page in the content tree.
3. On the **Properties -> Security** tab in the **Access** section switch **Requires SSL** to **Yes**.
4. Click **Save**.

Now all users attempting to access the page will always be redirected to the HTTPS version of the page's URL.

### Securing the administration interface

You may enable that all pages belonging to the administration interface will be accessible only through the SSL protocol.

1. Navigate to **Settings -> Security & Membership**.
2. In the **Administration** category, select the **Use SSL for administration interface** field.
3. 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.

> **Note:** 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.