Known issues
This section lists the known issues of this release, but is not a complete list. For inquiries about a particular bug, please contact Technical Support within the FortiCare portal.
|
Bug ID |
Description |
|---|---|
|
970973 |
Soft RAID-10 is not supported. |
|
969403 |
When creating a target, the default Target Only template is not in the GUI. |
|
969964 |
FortiAnalyzer log: Secret logs are not ordered by Time or Token Id. |
|
971485 |
A disabled TOTP key could not be recovered from GUI except by providing the same shared key. |
|
974134 |
Unable to log in to iDrac if Web Proxy is enabled. |
|
975443 |
A new tagging feature added to FortiClient build 907 and above may cause the ZTNA feature not to work in FortiPAM. |
|
978393 |
Support AWS root and IAM users on Web Proxy. |
|
970329 |
The standalone FortiClient requires the PC to reboot to start up after shutdown. |
|
982033 |
Native launchers fail after upgrading the standalone FortiClient from a previous version. For workaround, see Native launchers failure in Special notices. |
|
982710 |
Launch Secret is not available on the Secret Details page when the Inherit Permission option is disabled on the Firefox browser. Workaround: Launch the secret from the Secrets List page using the Launch Secret option if the Launch Secret option is not available on the Secret Details page. Alternatively:
|
|
985832 |
FortiPAM 1.2.0 does not support vTPM on GCP. |
|
984506 |
The sponsor admin does not have secret and video log access enabled by default after upgrading from FortiPAM 1.1.2 to 1.2.0. Workaround: Rebooting the system enables View Secret Log and View Secret Video permissions for the sponsor admin. |
|
986168 |
Only first entry shows up in User Permission for a secret target. |