Fortinet Document Library

Version:


Table of Contents

New Features

7.0.0
Download PDF
Copy Link

Local certificate wizard 7.0.2

The certificate wizard is used to add local certificates by either provisioning them through ACME, generating them using the self-signed Fortinet_CA_SSL CA certificate, or importing a server certificate signed by a public or private CA.

Using the certificate wizard to generate a new certificate allows you to use the built-in local CA certificate Fortinet_CA_SSL to sign the new server certificate. You can specify the CN and SAN fields to indicate the trusted FQDN or IP address. The new server certificate can be used in various places, such as for SSL VPN web and tunnel access, or HTTPS administrator portal access. For Web access, end users must import the Fortinet_CA_SSL certificate to trust the certificate chain so that the browser does not show warning messages when connecting.

When generating a new certificate on the VPN > SSL-VPN Settings page, the Common name and Subject alternate name fields are pre-filled with the address from the SSL-VPN listening interface.

The following examples demonstrate generating a certificate for administrative portal GUI access and generating a server certificate for SSL VPN.

Generating a server certificate for SSL VPN

In this example, the customer needs to configure web mode SSL VPN with a valid certificate that is signed by the FortiGate CA. As the FortiGate SSL VPN interface has multiple IP addresses, and an FQDN that resolves to the primary IP address, the certificate must be valid when accessing it with different domains or IP addresses.

The port2 interface is mapped to the SSL VPN interface, and has multiple IP addresses:

  • Primary: 10.1.100.2/24

  • Secondary: 10.1.100.192/32 and 10.1.100.202/24

User u1 on PC1 can access the SSL VPN portal by going to:

  • https://fgt401e.sslvpn.com:1443 - fgt401e.sslvpn.com resolves to the primary IP address.

  • https://10.1.100.202:1443

To configure the basic SSL VPN settings:
  1. Create a local user:

    1. Go to User & Authentication > User Definition and click Create New.

    2. Select Local User then click Next.

    3. Set username to u1 and enter a Password, then click Next.

    4. Click Next, then click Submit.

  2. Create an SSL VPN portal:

    1. Go to VPN > SSL-VPN Portals and click Create New.

    2. Set Name to testportal1.

    3. Disable Tunnel Mode and enable Web Mode.

    4. Click OK.

  3. Configure the SSL VPN settings:

    1. Go to VPN > SSL-VPN Settings.

    2. Enable SSL-VPN.

    3. Set Listen on Interface(s) to port2.

    4. Set Listen on Port to 1443.

    5. In the Authentication/Portal Mapping table:

      1. Click Create New.

      2. Set Users/Groups to u1.

      3. Set Portal to testportal1.

      4. Click OK.

      5. Edit All Other Users/Groups and set the Portal to an SSL-VPN portal.

    6. Click Apply.

  4. Create a firewall policy:

    1. Go to Policy & Objects > Firewall Policy and click Create New.

    2. Set the following:

      Name

      sslvpn1

      Incoming Interface

      SSL-VPN tunnel interface

      Outgoing Interface

      port1

      Source

      Address: all

      User: u1

      Destination

      Internal server IP address

      Service

      ALL

    3. Click OK.

To generate a new certificate for the SSL VPN portal:
  1. Go to VPN > SSL-VPN Settings.

  2. If Server Certificate is set to the default Fortinet_Factory certificate, a warning is shown. Click Create Certificate in the warning. You can also click Create in the certificate drop-down menu.

  3. Click Generate Certificate.

  4. The Common name is automatically set to the primary IP address of the listening interface. The Subject alternative name is set to secondary IP addresses of the listening.

  5. Set Certificate name to fgt401e.common.

  6. Change Common name to the FQDN fgt401e.sslvpn.com.

  7. Click Create.

  8. To view the details of the new certificate, click View Details. The Subject CN and SAN correspond to the configured values.

    The certificate is issued and signed by the FortiGate CA with the built-in Fortinet_CA_SSL certificate.

  9. Click Close.

  10. Click Download CA Certificate.

    End users must import this to their certificate store to trust the certificate chain when connecting to the SSL VPN.

  11. Click OK.

  12. Set Server Certificate to the new fgt401e.common certificate.

  13. Click Apply.

To test the certificate:
  1. On the client PC1, install the CA certificate that was downloaded from the FortiGate.

  2. In a browser, access the SSL VPN portal using the FQDN https://fgt401e.sslvpn.com.

    No certificate warning appears when accessing the page, and user u1 can log in and connect to the internal server.

  3. Open the certificate information, usually by clicking on an icon to the left of the URL. Note that the certificate is issued to the FQDN address and by the FortiGate CA.

  4. In a browser, access the SSL VPN portal using the secondary IP address https://10.1.100.202:1443. The same results are seen, as the IP address in defined in the Subject alternate name field.

Generating a server certificate for HTTPS administrative access

In this example, the customer needs to secure their external HTTPS administrative access by creating and applying a server certificate that is signed by the FortiGate CA. Administrators that have the CA certificate installed will not get a certificate warning when they access the HTTPS administrative portal.

The administrator accesses the FortiGate on port3, which uses DDNS that is configured on the FortiGate to map the FQDN gui.fgt401e.sslvpn.com to the interface address. The administrator can also access the GUI on port2 on 10.1.100.2.

To generate a new certificate for the HTTPS administrative portal:
  1. Go to System > Certificates and click Create/Import > Certificate.

  2. Click Generate Certificate.

  3. Set Certificate name to fgt401e.https.

  4. Set Common name to gui1.fgt401e.sslvpn.com.

  5. Set Subject alternative name to 10.1.100.2.

  6. Click Create.

  7. To view the details of the new certificate, click View Details. The CN and SAN correspond to the configured values.

  8. Click Close.

  9. Click Download CA Certificate to download the CA certificate to the management computer.

  10. Click OK.

  11. To apply the new certificate:

    1. Go to System > Settings.

    2. Set HTTPS server certificate to fgt401e.https.

    3. Click Apply.

      The certificate wizard could also have been accessed from the System > Settings page by clicking Create Certificate in the certificate warning (if shown) or by clicking Create the drop-down menu.

To test the certificate:
  1. On the client PC1, install the CA certificate that was downloaded from the FortiGate.

  2. In a browser, access the HTTPS administrative portal using the FQDN https://gui1.fgt401e.sslvpn.com.

    No certificate warning appears when accessing the page.

  3. Open the certificate information, usually by clicking on an icon to the left of the URL. Note that the certificate is issued to the FQDN address and by the FortiGate CA.

  4. In a browser, access the HTTPS administrative portal on https://10.1.100.2. The same results are seen, as the IP address in defined in the Subject alternate name field.

Local certificate wizard 7.0.2

The certificate wizard is used to add local certificates by either provisioning them through ACME, generating them using the self-signed Fortinet_CA_SSL CA certificate, or importing a server certificate signed by a public or private CA.

Using the certificate wizard to generate a new certificate allows you to use the built-in local CA certificate Fortinet_CA_SSL to sign the new server certificate. You can specify the CN and SAN fields to indicate the trusted FQDN or IP address. The new server certificate can be used in various places, such as for SSL VPN web and tunnel access, or HTTPS administrator portal access. For Web access, end users must import the Fortinet_CA_SSL certificate to trust the certificate chain so that the browser does not show warning messages when connecting.

When generating a new certificate on the VPN > SSL-VPN Settings page, the Common name and Subject alternate name fields are pre-filled with the address from the SSL-VPN listening interface.

The following examples demonstrate generating a certificate for administrative portal GUI access and generating a server certificate for SSL VPN.

Generating a server certificate for SSL VPN

In this example, the customer needs to configure web mode SSL VPN with a valid certificate that is signed by the FortiGate CA. As the FortiGate SSL VPN interface has multiple IP addresses, and an FQDN that resolves to the primary IP address, the certificate must be valid when accessing it with different domains or IP addresses.

The port2 interface is mapped to the SSL VPN interface, and has multiple IP addresses:

  • Primary: 10.1.100.2/24

  • Secondary: 10.1.100.192/32 and 10.1.100.202/24

User u1 on PC1 can access the SSL VPN portal by going to:

  • https://fgt401e.sslvpn.com:1443 - fgt401e.sslvpn.com resolves to the primary IP address.

  • https://10.1.100.202:1443

To configure the basic SSL VPN settings:
  1. Create a local user:

    1. Go to User & Authentication > User Definition and click Create New.

    2. Select Local User then click Next.

    3. Set username to u1 and enter a Password, then click Next.

    4. Click Next, then click Submit.

  2. Create an SSL VPN portal:

    1. Go to VPN > SSL-VPN Portals and click Create New.

    2. Set Name to testportal1.

    3. Disable Tunnel Mode and enable Web Mode.

    4. Click OK.

  3. Configure the SSL VPN settings:

    1. Go to VPN > SSL-VPN Settings.

    2. Enable SSL-VPN.

    3. Set Listen on Interface(s) to port2.

    4. Set Listen on Port to 1443.

    5. In the Authentication/Portal Mapping table:

      1. Click Create New.

      2. Set Users/Groups to u1.

      3. Set Portal to testportal1.

      4. Click OK.

      5. Edit All Other Users/Groups and set the Portal to an SSL-VPN portal.

    6. Click Apply.

  4. Create a firewall policy:

    1. Go to Policy & Objects > Firewall Policy and click Create New.

    2. Set the following:

      Name

      sslvpn1

      Incoming Interface

      SSL-VPN tunnel interface

      Outgoing Interface

      port1

      Source

      Address: all

      User: u1

      Destination

      Internal server IP address

      Service

      ALL

    3. Click OK.

To generate a new certificate for the SSL VPN portal:
  1. Go to VPN > SSL-VPN Settings.

  2. If Server Certificate is set to the default Fortinet_Factory certificate, a warning is shown. Click Create Certificate in the warning. You can also click Create in the certificate drop-down menu.

  3. Click Generate Certificate.

  4. The Common name is automatically set to the primary IP address of the listening interface. The Subject alternative name is set to secondary IP addresses of the listening.

  5. Set Certificate name to fgt401e.common.

  6. Change Common name to the FQDN fgt401e.sslvpn.com.

  7. Click Create.

  8. To view the details of the new certificate, click View Details. The Subject CN and SAN correspond to the configured values.

    The certificate is issued and signed by the FortiGate CA with the built-in Fortinet_CA_SSL certificate.

  9. Click Close.

  10. Click Download CA Certificate.

    End users must import this to their certificate store to trust the certificate chain when connecting to the SSL VPN.

  11. Click OK.

  12. Set Server Certificate to the new fgt401e.common certificate.

  13. Click Apply.

To test the certificate:
  1. On the client PC1, install the CA certificate that was downloaded from the FortiGate.

  2. In a browser, access the SSL VPN portal using the FQDN https://fgt401e.sslvpn.com.

    No certificate warning appears when accessing the page, and user u1 can log in and connect to the internal server.

  3. Open the certificate information, usually by clicking on an icon to the left of the URL. Note that the certificate is issued to the FQDN address and by the FortiGate CA.

  4. In a browser, access the SSL VPN portal using the secondary IP address https://10.1.100.202:1443. The same results are seen, as the IP address in defined in the Subject alternate name field.

Generating a server certificate for HTTPS administrative access

In this example, the customer needs to secure their external HTTPS administrative access by creating and applying a server certificate that is signed by the FortiGate CA. Administrators that have the CA certificate installed will not get a certificate warning when they access the HTTPS administrative portal.

The administrator accesses the FortiGate on port3, which uses DDNS that is configured on the FortiGate to map the FQDN gui.fgt401e.sslvpn.com to the interface address. The administrator can also access the GUI on port2 on 10.1.100.2.

To generate a new certificate for the HTTPS administrative portal:
  1. Go to System > Certificates and click Create/Import > Certificate.

  2. Click Generate Certificate.

  3. Set Certificate name to fgt401e.https.

  4. Set Common name to gui1.fgt401e.sslvpn.com.

  5. Set Subject alternative name to 10.1.100.2.

  6. Click Create.

  7. To view the details of the new certificate, click View Details. The CN and SAN correspond to the configured values.

  8. Click Close.

  9. Click Download CA Certificate to download the CA certificate to the management computer.

  10. Click OK.

  11. To apply the new certificate:

    1. Go to System > Settings.

    2. Set HTTPS server certificate to fgt401e.https.

    3. Click Apply.

      The certificate wizard could also have been accessed from the System > Settings page by clicking Create Certificate in the certificate warning (if shown) or by clicking Create the drop-down menu.

To test the certificate:
  1. On the client PC1, install the CA certificate that was downloaded from the FortiGate.

  2. In a browser, access the HTTPS administrative portal using the FQDN https://gui1.fgt401e.sslvpn.com.

    No certificate warning appears when accessing the page.

  3. Open the certificate information, usually by clicking on an icon to the left of the URL. Note that the certificate is issued to the FQDN address and by the FortiGate CA.

  4. In a browser, access the HTTPS administrative portal on https://10.1.100.2. The same results are seen, as the IP address in defined in the Subject alternate name field.