Resolved Issues
This section lists the resolved issues in v30.9.737.
| ID | Description |
|---|---|
| FN-3106 | Usability: Resolved an issue where proxy/PAC configuration was not properly cleared when Web was disabled via the Endpoint Management profile. |
| FN-3049 | Upgrade: Resolved an issue where proxy/PAC configuration was not properly cleared, leading to repeated auth prompts or broken connectivity during/after agent upgrade. |
| FN-3001 | Upgrade: Resolved an issue when upgrading from F1E to Forcepoint Agent, where a reboot is required and not performed to complete the upgrade and OTA pushed a newer version, resulting in an incomplete install of the agent. Now, OTA upgrades will not occur until the agent is in a state where the upgrade can proceed. |
| FN-2932 | Resolved an issue where policy rules using classifiers derived from predefined classifiers failed to trigger incident matches on the endpoint. |
| FN-2884 | Web Security: Resolved an issue with Proxy Connect installs where the Username UPN was not getting sent to the Proxy from the agent for Azure-AD-joined devices |
| FN-2842 | DLP Policy Enforcement: Resolved an issue where updated dependency files for new DLP Classifiers were not getting propagated to the Endpoint. |
| FN-920 | Web Security: Resolved an issue where the Web Security mode set in the Web Security portal was not taking effect on the Endpoint. Now the mode set (proxy connect or direct connect)
will change the agent's running state after a reboot. Note: If the mode is set to auto, this will result in the agent running in proxy connect mode.
|
| FN-838 | Web Security: Fixed an issue where the Forcepoint Agent in PCEP Fallback Mode set to "Open" may cause an internet connection error instead of allowing unrestricted browsing — users were unable to access any websites while the endpoint was in fallback mode. |