Known issues
The following issues have been identified in version 24.1.56. For inquiries about a particular bug, contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
|
638426 |
For secure web gateway (SWG) users, loading some websites using cookie-based authentication or websites that do not allow redirection has issues. Workaround: customize PAC file that SWG users use to exempt affected websites. |
|
716833 |
FortiClient (macOS) does not support application-based split tunneling. |
|
746224 |
Clicking Deauthenticate for a 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. |
|
837391 |
Connected Users and Asset Map display 0.0.0.0/Unknown IP for VPN SSO users. |
|
888092 |
Changes made to a modified proxy policy may not always take effect. |
| 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. |
| 998070 | Only a root user can access Forensics services in a managed security service provider setup. |
|
1015248 |
Option to add and modify threat feeds may not always display on GUI. |
|
1019049 |
Message prompt does not display when requesting FortiClient debug logs from the Endpoint Details window. |