FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
jjdope
Staff
Staff
Article Id 363541
Description

 

This article describes a workaround to resolve the issue where the 'Install Preview' on a FortiManager always shows the 'Certificate Fingerprint' configuration instead of the actual changes made.

 

Scope

 

FortiManager, FortiClient EMS, FortiGate.

 

Solution

 

When the certificate is updated on the EMS server, it is updated on the FortiGate. FortiManager retrieves this data and updates its Device Database.

 

To apply changes, Configure any settings on the FortiManager. Then, push the configuration to the target FortiGate. Before completing the installation, select 'Install Preview'. Instead of reflecting the changes made, the preview will display the 'certificate fingerprint' configuration.

 

1.png

 

Resolution:

 

In the FortiManager, navigate to Device Manager -> Device & Groups -> The target FortiGate -> CLI Configurations -> Endpoint-Control -> fctems.

  • The updated certificate fingerprint will be displayed in this section.

 

Navigate to Fabric View -> Fabric Connectors -> fct ems-1 -> Advanced -> Certificate-fingerprint.

  • This section will contain the old certificate fingerprint.

 

2.png

 

Copy the certificate fingerprint from 'Device Manager -> Device & Groups -> Target FortiGate -> CLI Configurations -> Endpoint-Control -> fctems' and paste it to 'Fabric View -> Fabric Connectors -> fct ems-1 -> Advanced -> Certificate-fingerprint'.

 

Note:

FortiManager does not support importing fctems. It just always copies the ADOM database config to the device level.