This section highlights the major known issues discovered in FortiADC 5.3.5 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|Support private key with passphrase uploading in OCI
|Correct the error message in Health check monitor when the HTTP string mismatch
|Authentication Relay with “Domain Prefix Support” Failed for Kerberos User Principle Test
|Domain\username in Authentication Form treats backslash plus two following characters as hexcode
|Support Source IP in WAF Exception
|Unable to de-select a service (e.g. https, ping, etc.) from "allow access" for non-used interface on WebUI.
|Fix the DataTable warning on SLB MySQL Traffic Log
|Health Check status might be wrong in a certain circumstance with SNMP HC
|Health check on MySQL Slave is not accurate
|Sync-list not working from GUI
|Fnginx coredump in certain SLB MySQL circumstances
|SSH port forwarding exposes unprotected localhost/internal services
|Coredump by IP reputation
|The HTTP/2 configuration is unable to apply properly.
|crlupdated memory leak
|Read-only user is able to perform an action designated for a read-write user
|Vulnerable to XSS (New Dashboard name parameter not sanitized)
|"502 Bad gateway" error in HTTP/2 with quick refresh on the html page
|httproxy high CPU and crashes in certain circumstances
|"Invalid arguments." error is printed when adding more than 32 healthchecks to Server Pool.
|Correct the displaying of "maintain" status for SNMP Health Check in Fortiview