Resolved Issues
The following issues have been fixed in 7.4.11. For inquires about a particular bug, please contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
|
1273378 |
FortiPortal install in more then one FortiGate generates "No permission to access task id xxx". |
|
1207145 |
FortiPortal using port 443 to connect FortiManager_Sec, which lead to unhealthy status, while both FortiManager HA cluster nodes are using ports other than 443. |
|
1228821 |
Confusing messages in policy installation logs. |
|
1296587 |
Device auto enrollment shows error when created. |
|
1283974 |
FortiPortal uses port 443 to check FortiManager health when FortiManager HA cluster uses another port, which leads to Unhealthy status. |
| 1295721 | FortiSwitch and FortiAPs are not visible on FortiPortal but are visible on FortiManager. |
|
1263208 |
Install preview shows extra changes when modifying single policy on customer portal with FortiManager 7.4.9 and 7.4.10. |
| 1263253 | Managed Endpoint page is blank when Root/Computer Workgroup objects are added for FortiClient EMS. |
|
1274588 |
Performance problems with large scale customers. |
|
1289404 |
Query FortiPortal AWS deployment IMDSv1 and IMDSv2. |
|
1237752 |
Scalable cluster failover events consume more disk space than previously required. |