Description | This article describes a known restriction that occurs when importing end-entity certificates onto the FortiGate while FIPS-CC mode is enabled. |
Scope | FortiGate, FIPS-CC. |
Solution |
When FIPS-CC mode is enabled, FortiOS does not allow administrators to import an end-entity certificate if the Root and Intermediate certificates (if any) used to sign the certificate are missing on the FortiGate. This is a known restriction imposed as part of NDcPP v2.2e (FIA_X509_EXT.3.2) requirements while in FIPS-CC mode, whereas non-FIPS-enabled FortiGates do not have this restriction.
For example, consider the following example:
If the administrator attempts to do this in the Web GUI, an error message will be received stating 'CRL/certificate file doesn't have matched CA imported'.
To resolve this, the full certificate chain must be imported to the FortiGate. This includes the Root CA certificate as well as any Intermediate CA certificates used to sign the FortiGate certificate. To do this:
Once the CA certificates have been imported, the end-entity certificate for the FortiGate will be able to be imported (Create/Import -> Certificate).
While this scenario generally occurs with private Certificate Authorities (i.e. owned/operated within a private business), it can still occur with well-known public Certificate Authorities on occasion (i.e. the FortiGuard Certificate Bundle provided to the FortiGate could be missing the root/intermediate CA certificates required). In those cases, CA certificate files can frequently be retrieved directly from the Certificate Authority over the Internet.
Related links: DigiCert Trusted Root Authority Certificates GoDaddy Certificate Repository
Related articles: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.