Known issues
The following issues have been identified in version 24.2.12. For inquiries about a particular bug, contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
|
716833 |
FortiClient (macOS) does not support application-based split tunneling. |
|
746224 |
Clicking Deauthenticate for a secure web gateway (SWG) user in Session Monitor does not deauthenticate the user. |
|
749159 |
FortiSASE performs SWG authentication via HTTP. Therefore, single sign on (SSO) authentication is strongly recommended for SWG users. |
|
775860 |
When installing FortiClient 7.0.8 on Windows, user may see a warning about FortiClient originating from an unknown publisher if Windows Defender is enabled. |
| 907570 | FortiSASE currently does not support option to test SAML connectivity for SWG SSO. |
| 914278 | Managed Endpoints incorrectly displays warning for FortiClient version mismatch for iOS and Android devices. |
|
964123 |
Custom endpoint profiles cannot use LDAP server configured before FortiSASE instance upgrade to 23.4. Workaround: edit existing LDAP server configuration from first page and reenter credentials. See Profiles for details. |
|
1019049 |
Message prompt does not display when requesting FortiClient debug logs from the Endpoint Details window. |
|
1021927, 1023394 |
For SWG users, loading some social media websites that do not allow redirection has issues. Workaround: customize PAC file that SWG users use to exempt affected websites. |
| 1025669 | VPN SAML SSO using external browser authentication may work inconsistently using Chrome that has TLS 1.3 hybridized Kyber support enabled. Firefox works as expected |
|
1028107 |
FortiSASE may generate some scheduled reports later than scheduled.
|