Resolved Issues
The following issues have been fixed in version 3.2.0. For inquiries about a particular bug, contact Customer Service & Support.
Resolved issues
Bug ID |
Description |
---|---|
573390 |
LDAP wildcard administrators do not support AD groups. |
578402 |
FortiSandbox does not exclude whitelist from malware package. |
578434 |
FortiSandbox does not give confirmation ID in the log. |
579978 |
Restored configuration restores unprocessed alert setting. |
583569 |
The administrator with token authorization fails to test login. |
583897 |
The connection fails if you use FortiManager as the web filter server. |
584257 |
The setting from CLI command |
584772 |
Creating a new Bit9 adapter causes the GUI to crash. |
595761 |
The CLI command |
597427 |
FortiClient cannot connect to FortiSandbox. |
601190 |
The downloaded file from the embedded URL in a HTML file isn’t sent to the sandbox for scan. |
602846 |
Job details don't display Static File Scan(AI) if the job is rated by static scan and AI is on. |
603939 |
FortiSandbox Azure does not support using service principal (the Client ID). |
612620 |
FortiSandbox Azure does not delete VM clone and relative resources after the VM is deleted from the GUI. |
612621 |
FortiSandbox Azure creates public IP on customized VM clone. |
612628 |
FortiSandbox Azure loses installed customized VMs if it is stopped and started from Azure portal manually. |