Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Administration Guide

    Home FortiWeb 7.0.9 Administration Guide
    7.0.9
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.10
    7.2.9
    7.2.8
    7.2.7
    7.2.6
    7.2.5
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.10
    7.0.9
    7.0.8
    7.0.6
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.2
    6.4.1
    6.4.0
    6.3.23
    6.3.19
    6.3.18
    6.3.17
    6.3.16
    6.3.15
    6.3.14
    6.3.13
    6.3.11
    6.3.10
    6.3.9
    6.3.7
    6.3.6
    6.3.5
    6.3.4
    6.3.3
    6.3.2
    6.3.1
    6.3.0
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.2
    6.1.1
    5.7.0
    5.6.1
    5.6.0
    5.6.0

    Local certificates

    Local certificates

    Server Objects > Certificates > Local displays all X.509 server certificates that are stored locally, on the FortiWeb appliance, for the purpose of offloading or scanning HTTPS.

    Generate Click to generate a certificate signing request. For details, see Local certificates.
    Import Click to upload a certificate. For details, see Local certificates.
    View Certificate Detail Click to view the selected certificate’s subject, range of dates within which the certificate is valid, version number, serial number, and extensions.
    Download

    Click to download the selected CSR’s entry in certificate signing request (.csr) file format.

    This button is disabled unless the currently selected file is a CSR.
    Edit Comments Click to add or modify the comment associated with the selected certificate.
    (No label. Check box in column heading.)

    Click to mark all check boxes in the column, selecting all entries.

    To select an individual entry, instead, mark the check box in the entry’s row.
    Name Displays the name of the certificate.
    Subject

    Displays the distinguished name (DN) located in the Subject: field of the certificate.

    If the row contains a certificate request which has not yet been signed, this field is empty.
    Comments Displays the description of the certificate, if any. Click the Edit Comments icon to add or modify the comment associated with the certificate or certificate signing request.
    Status

    Displays the status of the certificate.

    • OK—Indicates that the certificate was successfully imported. To use the certificate, select it in a server policy or server pool configuration.
    • PENDING—Indicates that the certificate request has been generated, but must be downloaded, signed, and imported before it can be used as a server certificate.

    FortiWeb presents a server certificate when any client requests a secure connection, including when:

    • Administrators connect to the web UI (HTTPS connections only)
    • Clients use SSL or TLS to connect to a virtual server, if you enabled SSL offloading in the policy (HTTPS connections and Reverse Proxy mode only)

    Although it does not present a certificate during SSL/TLS inspection, FortiWeb still requires server certificates in order to decrypt and scan HTTPS connections traveling through it (SSL inspection) if operating in any mode except Reverse Proxy. Otherwise, FortiWeb will not be able to scan the traffic, and will not be able to protect that web server.

    If you want clients to be able to use HTTPS with your website, but your website does not already have a server certificate to represent its authenticity, you must first generate a certificate signing request. For details, see Local certificates. Otherwise, start with Local certificates.

    See also
    Previous
    Next

    Local certificates

    Local certificates

    Server Objects > Certificates > Local displays all X.509 server certificates that are stored locally, on the FortiWeb appliance, for the purpose of offloading or scanning HTTPS.

    Generate Click to generate a certificate signing request. For details, see Local certificates.
    Import Click to upload a certificate. For details, see Local certificates.
    View Certificate Detail Click to view the selected certificate’s subject, range of dates within which the certificate is valid, version number, serial number, and extensions.
    Download

    Click to download the selected CSR’s entry in certificate signing request (.csr) file format.

    This button is disabled unless the currently selected file is a CSR.
    Edit Comments Click to add or modify the comment associated with the selected certificate.
    (No label. Check box in column heading.)

    Click to mark all check boxes in the column, selecting all entries.

    To select an individual entry, instead, mark the check box in the entry’s row.
    Name Displays the name of the certificate.
    Subject

    Displays the distinguished name (DN) located in the Subject: field of the certificate.

    If the row contains a certificate request which has not yet been signed, this field is empty.
    Comments Displays the description of the certificate, if any. Click the Edit Comments icon to add or modify the comment associated with the certificate or certificate signing request.
    Status

    Displays the status of the certificate.

    • OK—Indicates that the certificate was successfully imported. To use the certificate, select it in a server policy or server pool configuration.
    • PENDING—Indicates that the certificate request has been generated, but must be downloaded, signed, and imported before it can be used as a server certificate.

    FortiWeb presents a server certificate when any client requests a secure connection, including when:

    • Administrators connect to the web UI (HTTPS connections only)
    • Clients use SSL or TLS to connect to a virtual server, if you enabled SSL offloading in the policy (HTTPS connections and Reverse Proxy mode only)

    Although it does not present a certificate during SSL/TLS inspection, FortiWeb still requires server certificates in order to decrypt and scan HTTPS connections traveling through it (SSL inspection) if operating in any mode except Reverse Proxy. Otherwise, FortiWeb will not be able to scan the traffic, and will not be able to protect that web server.

    If you want clients to be able to use HTTPS with your website, but your website does not already have a server certificate to represent its authenticity, you must first generate a certificate signing request. For details, see Local certificates. Otherwise, start with Local certificates.

    See also
    Previous
    Next