"local-standalone" and "local-authentication" features are inconsistent with FortiOS/FortiGate.

SAML account with remote certificate not getting imported to FortiManager-Cloud.

Certificate enrollment fails using SCEP on Microsoft server with sub-ca certificate chains.

System Template cannot be assigned to a device as a member of a device group when the required meta-fields are used.

When VDOM is enabled, FortiManager shows multiple firmware templates on Device Manager with different status.

Error message peer must be set can be seen when configuring the IPSec Tunnel Templates.

Unable to configure more than one IP addresses for "vrdst" under the "interface vrrp" setting.

Unable to create route map rule using 'match-interface' when using the BGP Templates under the Provisioning Templates.

Speedtest and speedtest-bypass-routing under SD-WAN templates configuration cannot be set on FortiManager.

Installation fails due to the unexpected system interface config changes for "pvc" related settings.

The view device revision under Revision History does not display the full and complete device's configuration.

Several unregistered FortiGates consume FortiManager's resources thus FortiManager becomes very slow and unresponsive.

FortiManager does not update its Fortigate's IP address in case the IP gets modified on the FortiGate.

Unable to create simultaneous static routes with named address objects.

Removing VLANs from zones and adding a new VLAN to the same zone deletes that Zone.

Creating the interface type Software Switch throws an error when adding a VLAN interface as a member.

It is not possible to select all objects filtered by the search under Device Manager.

Special characters in Meta fields are displayed in HTML Numeric Code.

Unable to install VPN psk with special characters through CLI template.

Failed to reload the configuration due to the "datasrc invalid" error message.

"OPEN" mode is missing from the System Template's WIFI SSID.

Duplicate CSF groups for 7.0 FGTs (7.0.2+) due to syntax returning upstream-ip instead of upstream.

FortiManager doesn't show the filter configuration for syslogd correctly.

Installation filed due to the config wireless-controller SNMP settings.

After upgrading the global ADOM, installation failed due to the custom ssl-ssh-profile config.

Unable to upgrade an ADOM from 6.2 to 6.4.

FortiManager holds the wrong value for AP limit of the FG-80F.

FortiManager does not sent the proper response for SNMP request to the fmDeviceEntSupportState query.

HA Configuration in Zero-touch provisioning (ZTP) does not synchronize to the secondary FortiGate.

diag cdb upgrade force-retry del-invalid-ref never stops.

ADOM upgrade fails due to the virtual wire pair policy.

Unable to export update manager log files for the sftp fdssvrd.

"Interface Bandwidth" widget is displayed in ADOM 6.2 in 6.4 FortiManager's version.

FortiManager configured in closed network was unable to fetch the FGD DBs which was previously manually saved on another closed network FortiManager.

Unable to add/modify a FPX 'Explicit Proxy' policy from a FortiProxy ADOM in FortiManager.

Extremely slow performance when fetching all the devices from DVM via JSON API.

Upgrading HA cluster via FortiManager stays members into a restart loop.

FortiManager has some unsupported commands for the fortitoken user definition.

ADOMs created by XML API cannot be locked or unlocked.

The App Control set to Monitor in FortiManager causes the app to disappear from FortiGate.

Remote VPN certificate installation failed and cert disappeared from FortiManager however on the FortiGate the certificate installed successfully.

Policy Check export does not have the last hit count details anymore.

There is not any warning messages when assigning already in used normalized interface.

FortiManager may not import all the roles and address groups from ClearPass.

Installation fails when Any has been set as incoming interface and VIP is being used on the IPV4 firewall policy.

When modifying the IP address of the default VPN interface of a spoke in Device Manager, hub remote gateway should be modified to reflect that change.

Policy package install skips the policy where destination interface is set as SD-WAN zone and policy is IPSEC policy.

Policy package import fails due to the 'Device mapping::"query failed."' error.

Copy procedure fails without any proper and clear error messages.

Searching members inside an address group does not work.

Unable to complete the Cisco pxGrid fabric connector's configuration on FortiManager.

Unable to change the action field for the default IPS profile and their clones.

FortiManager fails to install the custom signature because it is too long.

FortiManager may now differentiate between the ISDB objects "Predefined Internet Services" and "IP Reputation Database".

Unable to create more than 20 SAML users in policy package object.

In workspace mode, locking and unlocking ADOMs displays a blank page when classic dual pane is enabled.

FortiManager purges the "arrp-profile" when installing the v6.2 policy packages to v6.4 FortiGates.

6.4 version ADOM policy package failed to enable policy NAT from GUI.

Installation failed when using custom-deep-inspection.

Installation failed after upgrading ADOM from 6.2 to 6.4.

Installation fails when trying to install SAML user configuration.

The Policy package counter field does not display the number of modified policy packages.

Modifying the "Sections" under the Policy&Objects leads to some unexpected changes/behavior.

Wrong direction definition has been displayed for "Tor-Relay.Node" ISDB object.

"Synchronize Firewall Addresses" under the FortiClient EMS Connector does not automatically create and synchronize addresses for all EMS tags.

Re-assignment of tokens in FortiManager policy and objects, deletes and re-adds the firewall policies that are used those objects.

Policy Consistency Check fails due to the firewall service's name.

The export policy feature displays limited numbers of the group objects.

Installation failed due to "Copy global shared objects" failure.

Auto-asic-offload cannot be disabled for the first time in the policy.

FortiManager's Policy Package diff displays policy objects change even though there is not any changes.

Installation failed due to the wrong FortiSwitch VLAN type for the default NAC and nac_segment VLANs.

After the 6.0 ADOM upgrade, installing the same v6.0 policy package got "unset webfilter-profile" in wanopt proxy policy.

Verification fails due to the "resource-limits.proxy".

Failed to run the Post-Run CLI Template due to the "datasrc invalid" error.

FortiManager doesn't have the proper version string of FortiGate's IPGeo information.

FortiManager does not recognize the entitlement file for some FortiGates.

FortiManager cannot download the latest IPS DB.

"fmDeviceEntSupportState" OID returns incorrect value for some devices.

FortiManager displays wrong admin name under task monitor for firmware upgrade task.

FortiManager should be able to set desired permissions for Extender Manager in administrator profile settings.

SNMPv3 security option configuration has discrepancy between GUI and CLI.

The Mode option is not always available for root ADOM in all GUI-based root ADOM properties editing methods.

Webfiltering HTTPS 8888 is not working after FortiManager upgraded from 6.4.7 to 7.0.4.

FortiManager loads the "Administrator" list under the System Setting very slowly.

When Advanced ADOM Mode is enabled, FortiManager under the Device Inventory displays all devices from all VDOMs.

FortiManager does not synchronize with NTP server.

Not able to disable the trusted hosts from the GUI.

IPSec VPN Authusergrp option "Inherit from Policy" is missing when setting xauthtype as auto server.

Bookmark setting under the SSLVPN portal has some missing screen/color configuration.

Installation becomes very slow when FortiManager acts as CA server.