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 |
|---|---|
|
1002990 |
Web Account not responding after being idle for 10 minutes if recording is disabled. |
|
1009075 |
Failed to launch Azure as the password cannot be filled. Workaround:
|
|
1014549 |
WebSSH TOTP for FortiProduct. |
|
1003972 |
Fortinet Privileged Access Agent- MobaXterm Launch failure. |
|
970315 |
Support importing secret target and secret from files. |
|
1001231 |
The FortiPAM installation package does not include the Fortinet Privileged Access Agent for the Firefox browser. You can download it on https://www.fortinet.com/support/product-downloads. |
|
970973 |
Soft RAID-10 is not supported. |
|
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. |
|
978393 |
Support AWS root and IAM users on Web Proxy. |
|
970329 |
The standalone FortiClient requires the PC to reboot to start up after shutdown. |
|
1007952 |
After changing the Remote Group/Server option when editing a SAML user from a SAML server to a SAML group, the Force SAML Login option is disabled. |