Resolved issues

The following issues have been resolved in FortiADC 8.0.0 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID	Description
1151892	Adaptive Learning related crash when processing HTTP2 requests.
1145394	Configured DNS settings are overridden by default nameserver in AWS.
1131903	FortiADC returns <MISSING> in the SNMP response for sysinfo queries, resulting in incomplete system information retrieval.
1127125	IPv6 fragments from real server (RS) responses are reassembled at the virtual server (VS) but are not re-fragmented when forwarded to the client, causing transmission failure due to MTU checks. This creates a directional inconsistency, as fragmentation is not supported on the VS-to-client path.
1122454	Certificates are incorrectly deleted from the Local Certificate group when ACME encounters group members with missing or invalid IDs.
1120679	Oracle health check stops working due to a memory leak caused by unfreed lists and buffers after pthread_kill, leading to resource exhaustion over time.
1120666	After upgrading from 7.4.x to 7.6.1, the GUI incorrectly displays the hardware license status as "Unknown support (Expires: Unknown)", despite valid licensing.
1120243	FortiADC 1200F reports incorrect traffic and packet counter values in SNMP and CLI due to improper interface name handling, leading to discrepancies in monitoring data.
1119257	HA fails to establish between FortiADC nodes on firmware version 7.4.7 B0378 due to heartbeat message decoding errors, preventing synchronization between FortiADC-1 and FortiADC-2 KVM nodes.
1117823	The "Timeout UDP Session" field is incorrectly shown in the GUI when Stateless mode is enabled for a UDP Application Profile.
1116520	HTTP/2 requests to a specific URL result in timeouts, whereas HTTP/1.1 works without issue. This is due to delays in data transmission caused by HTTP/2 waiting for window updates. Internal adjustments to httproxy's send-state flags were made to improve alignment with HTTP/2 flow control, reducing the likelihood of transmission stalls due to insufficient window size.
1116460	Memory issue due to unfreed LDAP structures before each check, leading to incremental memory usage increase and process termination.
1115210	Remote LDAP authentication fails when accessing via ConsolePort, as the admin_auth function is not triggered during login.
1112914	FortiADC attempts to connect to 8.8.8.8 on port 53 when the DNS is configured to 0.0.0.0, despite the DNS setting being invalid.
1112580	The ssl_client utility in BusyBox does not function correctly for real server health checks due to missing system entropy. This prevents successful SSL handshakes during checks.
1106109	Connected route not displaying in HA-VRRP due to insufficient rtmd receiving buffer size configuration.
1103348	FortiADC AntiVirus does not block the EICAR file during upload (HTTP PUT), but can block it during download (HTTP GET) due to lack of support for scanning HTTP PUT traffic.
1096464	FortiADC's SSH server public key length is insufficient. The recommended minimum RSA public key length is 2048 bits or greater.
1093020	REST-API allows token brute-force attacks and does not log failed login attempts, leading to potential security vulnerabilities.
1091639	Local certificate import fails when the passphrase for the private key contains a backslash (), which is not handled properly.
1091469	Health check status is not properly updated on the secondary device after an HA failover. When the secondary device is promoted to primary, the status in the logical topology is not reflected correctly, leading to a lack of visibility on service availability and no alerts for service changes.