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

    • Handbook

    Home FortiADC 6.2.6 Handbook
    6.2.6
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    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.1.4
    7.1.3
    7.1.2
    7.1.1
    7.1.0
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.6
    6.1.5
    6.1.4
    6.1.3
    6.1.2
    6.1.1
    6.1.0
    6.0.1
    6.0.0
    5.4.3
    5.4.2
    5.4.1
    5.4.0
    5.3.6
    5.3.5
    5.3.4
    5.3.3
    5.3.2
    5.3.1
    5.3.0
    5.2.7

    Validating certificates

    Validating certificates

    This section discusses the ways to validate client certificates and real server certificates from within the FortiADC system. It covers the following topics:

    Configure a certificate verification object

    To be valid, a client certificate must meet the following criteria:

    • Must not be expired or not yet valid
    • Must not be revoked by either certificate revocation list (CRL) or, if enabled, online certificate status protocol (OCSP)
    • Must be signed by a certificate authority (CA) whose certificate you have imported into the FortiADC appliance

    Certificate verification rules specify the CA certificates to use when validating client certificates, and they specify a CRL and/or OCSP server, if any, to use for certificate revocation checking.

    You select a certificate verification configuration object in the profile configuration for a virtual server or in a real-server-SSL profile. If the client presents an invalid certificate during the authentication phase of a SSL/TLS session initiation, the FortiADC system will not allow the connection.

    Before you begin:

    • You must have Read-Write permission for System settings.
    • You must have already created CA, OCSP or CRL configuration.

    After you have configured a certificate verification object, you can include it in a virtual server profile or a Real Server SSL Profile, and it will be used to validate certificates presented to FortiADC.

    Note: For the same certificate object you can configure multiple CRL files.
    To configure a certificate verification object:
    1. Go to System > Certificate > Verify.
    2. Click Create New to display the configuration editor.
    3. Complete the configuration as described in Certificate verify configuration.
    4. Click Save when done. The newly certificate verification object appears on the Verify page.
    5. Click the Edit icon in the far-right column (or double-click the entry) to open the configuration editor.
    6. In the Group Member panel, select the CA, OCSP, or CRL of interest.
    7. Click Save when done.

    Certificate verify configuration
    Settings Guidelines
    Name

    Enter a unique name for the certificate verification object that you are creating. Valid characters are A-Z, a-z, 0-9, _, and -. The maximum length is 35 characters. No space is allowed.
    verify-depth

    Note: CLI only.

    The default value is 1, but you may select any value from 0 to 255.
    customize-error-ignore

    Note: This option is available from the CLI only.

    Enable or disable customize-error-ignore. The option is disabled by default. If it's enabled, you are required to select the ca-ignore-errors and cert-ignore-errors, as described below.
    ca-ignore-errors

    Note: CLI only. When customize-error-ignore is enabled, the following options become available for you to choose from:

    • UNABLE_TO_GET_ISSUER_CERT
    • UNABLE_TO_GET_CRL
    • CERT_NOT_YET_VALID
    • CERT_HAS_EXPIRED
    • CRL_NOT_YET_VALID
    • CRL_HAS_EXPIRED
    • DEPTH_ZERO_SELF_SIGNED_CERT
    • SELF_SIGNED_CERT_IN_CHAIN
    • UNABLE_TO_GET_ISSUER_CERT_LOCALLY
    • UNABLE_TO_VERIFY_LEAF_SIGNATURE
    • CERT_CHAIN_TOO_LONG
    • INVALID_CA
    • INVALID_PURPOSE
    • CERT_UNTRUSTED
    • CERT_REJECTED

    Note: If customize-error-ignore is disabled (by default), the CLI shows the following:

    ca-ignore-errors: UNABLE_TO_GET_ISSUER_CERT UNABLE_TO_GET_CRL CERT_UNTRUSTED

    cert-ignore-errors

    Note: CLI only. When customize-error-ignore is enabled, the following options become available for you to choose from:

    • UNABLE_TO_GET_ISSUER_CERT
    • UNABLE_TO_GET_CRL
    • CERT_NOT_YET_VALID
    • CERT_HAS_EXPIRED
    • CRL_NOT_YET_VALID
    • CRL_HAS_EXPIRED
    • DEPTH_ZERO_SELF_SIGNED_CERT
    • SELF_SIGNED_CERT_IN_CHAIN
    • UNABLE_TO_GET_ISSUER_CERT_LOCALLY
    • UNABLE_TO_VERIFY_LEAF_SIGNATURE
    • CERT_CHAIN_TOO_LONG
    • INVALID_CA
    • INVALID_PURPOSE
    • CERT_UNTRUSTED
    • CERT_REJECTED

    Note: If customize-error-ignore is disabled (by default), the CLI shows the following:

    cert-ignore-errors: UNABLE_TO_GET_CRL

    Group Member
    CA Select a CA (Required).
    OCSP Select an OCSP (Optional).
    CRL Select a CRL (Optional).
    Previous
    Next

    Validating certificates

    Validating certificates

    This section discusses the ways to validate client certificates and real server certificates from within the FortiADC system. It covers the following topics:

    Configure a certificate verification object

    To be valid, a client certificate must meet the following criteria:

    • Must not be expired or not yet valid
    • Must not be revoked by either certificate revocation list (CRL) or, if enabled, online certificate status protocol (OCSP)
    • Must be signed by a certificate authority (CA) whose certificate you have imported into the FortiADC appliance

    Certificate verification rules specify the CA certificates to use when validating client certificates, and they specify a CRL and/or OCSP server, if any, to use for certificate revocation checking.

    You select a certificate verification configuration object in the profile configuration for a virtual server or in a real-server-SSL profile. If the client presents an invalid certificate during the authentication phase of a SSL/TLS session initiation, the FortiADC system will not allow the connection.

    Before you begin:

    • You must have Read-Write permission for System settings.
    • You must have already created CA, OCSP or CRL configuration.

    After you have configured a certificate verification object, you can include it in a virtual server profile or a Real Server SSL Profile, and it will be used to validate certificates presented to FortiADC.

    Note: For the same certificate object you can configure multiple CRL files.
    To configure a certificate verification object:
    1. Go to System > Certificate > Verify.
    2. Click Create New to display the configuration editor.
    3. Complete the configuration as described in Certificate verify configuration.
    4. Click Save when done. The newly certificate verification object appears on the Verify page.
    5. Click the Edit icon in the far-right column (or double-click the entry) to open the configuration editor.
    6. In the Group Member panel, select the CA, OCSP, or CRL of interest.
    7. Click Save when done.

    Certificate verify configuration
    Settings Guidelines
    Name

    Enter a unique name for the certificate verification object that you are creating. Valid characters are A-Z, a-z, 0-9, _, and -. The maximum length is 35 characters. No space is allowed.
    verify-depth

    Note: CLI only.

    The default value is 1, but you may select any value from 0 to 255.
    customize-error-ignore

    Note: This option is available from the CLI only.

    Enable or disable customize-error-ignore. The option is disabled by default. If it's enabled, you are required to select the ca-ignore-errors and cert-ignore-errors, as described below.
    ca-ignore-errors

    Note: CLI only. When customize-error-ignore is enabled, the following options become available for you to choose from:

    • UNABLE_TO_GET_ISSUER_CERT
    • UNABLE_TO_GET_CRL
    • CERT_NOT_YET_VALID
    • CERT_HAS_EXPIRED
    • CRL_NOT_YET_VALID
    • CRL_HAS_EXPIRED
    • DEPTH_ZERO_SELF_SIGNED_CERT
    • SELF_SIGNED_CERT_IN_CHAIN
    • UNABLE_TO_GET_ISSUER_CERT_LOCALLY
    • UNABLE_TO_VERIFY_LEAF_SIGNATURE
    • CERT_CHAIN_TOO_LONG
    • INVALID_CA
    • INVALID_PURPOSE
    • CERT_UNTRUSTED
    • CERT_REJECTED

    Note: If customize-error-ignore is disabled (by default), the CLI shows the following:

    ca-ignore-errors: UNABLE_TO_GET_ISSUER_CERT UNABLE_TO_GET_CRL CERT_UNTRUSTED

    cert-ignore-errors

    Note: CLI only. When customize-error-ignore is enabled, the following options become available for you to choose from:

    • UNABLE_TO_GET_ISSUER_CERT
    • UNABLE_TO_GET_CRL
    • CERT_NOT_YET_VALID
    • CERT_HAS_EXPIRED
    • CRL_NOT_YET_VALID
    • CRL_HAS_EXPIRED
    • DEPTH_ZERO_SELF_SIGNED_CERT
    • SELF_SIGNED_CERT_IN_CHAIN
    • UNABLE_TO_GET_ISSUER_CERT_LOCALLY
    • UNABLE_TO_VERIFY_LEAF_SIGNATURE
    • CERT_CHAIN_TOO_LONG
    • INVALID_CA
    • INVALID_PURPOSE
    • CERT_UNTRUSTED
    • CERT_REJECTED

    Note: If customize-error-ignore is disabled (by default), the CLI shows the following:

    cert-ignore-errors: UNABLE_TO_GET_CRL

    Group Member
    CA Select a CA (Required).
    OCSP Select an OCSP (Optional).
    CRL Select a CRL (Optional).
    Previous
    Next