| Description | This article explains the mechanism behind ADOM CA certificate creation in FortiManager. |
| Scope | FortiManager |
| Solution |
When installing a device's policy package for the first time, FortiManager will push the default CA certificate that was created in the ADOM and named after the ADOM's name.
As the ADOM CA certificate is named after the current ADOM name itself, a new ADOM CA certificate will be generated when renaming an ADOM:
As the CA certificates are considered an ADOM-level configuration, FortiManager will try to install the new CA certificate to all managed devices in the ADOM in their next policy package installation:
As this will clutter up both FortiManager and FortiGate with unnecessary CA certificates every time the ADOM is renamed, the CA certificates can be deleted from Policy & Objects -> Advanced -> CA Certificates to prevent them from being installed to FortiGate:
|
