Bug fixes
This release of the product includes these general bug fixes.
General
| ID | Description |
|---|---|
| BG-20996 | User Provisioning - Resolved an issue where the user provisioning via AD Agent, Auto-Provision, SCIM fails when the first_name is longer than 30 characters. |
| BG-21388 | GCP API Scanning - Resolved an issue where the Enable API scanning checkbox was greyed out even after filling out CSPM and GCP settings. |
| BG-22030 | API Logs - Resolved an issue where the API logs page displayed file status as public even though the files, stored in OneDrive/Sharepoint, were never shared publicly. |
| BG-22323 | Block Login Policy - Resolved an issue where the Block Login policy with Location set to IaaS Provider IPs and Action set to Block was not working. |
| BG-23269 | OneDrive API scanning - Resolved an issue where the API logs displayed incorrect file sharing status for the files stored in OneDrive. |
| BG-23271 | HTTP Request Headers - Resolved an issue where the HTTP Request Headers were not working with Group based policy for Google Workspace. |
| BG-23321 | Any HTTP/s ZTNA App/Service - Agentless ZTNA application name does not support quotation marks. |
| BG-23336 | Alerts - Resolved an issue where the page displayed inconsistent alert for the action applied. |
| BG-23516 | API logs - Resolved an issue where the Email To, Email CC or Email BCC filters were getting ignored in the API Summary logs page. |
| BG-23522 | API logs - Resolved an issue where the API Audit and Summary logs for OneDrive displayed the Shared With field for publicly shared files. |
| BG-23557 | API Logs - Resolved an issue where the API logs were missing for few files. |
| BG-23614 | Web logs - Resolved an issue where the REST API was not exporting Web logs even though Forcepoint ONE SSE UI shows deny Web logs. |
| BG-23842 | Discovery Reports - Resolved an issue where the Search the App Database option returns 0 results even though the report contains data of that application. |
| BG-23964 | Data Security Dashboard - Resolved an issue where the Volume Scanned widget displayed incorrect Sensitive value in the page. |
| BG-24095 | API logs - Resolved an issue where the API summary logs were displaying None entries instead of actual email/username. |
| BG-24129 | Web Logs - Resolved an issue where users were unable to export web logs and was displaying an error Could not generate CSV, please try again later. |
| BG-24262 | Web Logs - Resolved an issue where the Web logs page was displaying an error An error occurred, please try again while trying to filter logs other than denied for 30 days. |
| BG-24280 | API Logs - Resolved an issue where the API Audit/Summary logs were not loading and was displaying Unable to retrieve results, please contact Forcepoint One support error. |
| BG-24302 | Google Drive - Resolved an issue where the DLP engine was not prompting even after hitting the DLP policy when reuploading the file to Google Drive via web browser. |
| BG-24305 | API logs - Resolved an issue where users were unable to access publicly shared files in SharePoint using the link available in the API log without M365 authentication. |
| BG-24333 | API logs - Resolved an issue where DLP pattern match context was missing in the API logs even when the Capture context around DLP matches checkbox was enabled for the data pattern. |
| BG-24364 | Web logs - Resolved an issue where the REST API was not exporting Web logs even though Forcepoint ONE SSE UI shows Web logs. |
| BG-24412 | Web Logs - Resolved an issue where the denied web logs were not loading when the Action=Denied filter was applied, however denied web logs were displayed when you set username or transaction ID filters. |
| BG-24436 | Microsoft Outlook Calendar - Resolved an issue where users were unable to access Calendar intermittently from the Microsoft Outlook in web browser via reverse proxy. |
| BG-24452 | Cloud Applications in FSM - After successfully integrating the Forcepoint ONE CASB system with Forcepoint DLP, the cloud applications configured in Forcepoint ONE SSE were not getting retrieved and displayed under the page in FSM. Resolved this issue. |
| BG-24472 | Microsoft Teams - Resolved an issue where the Team Text DLP policy was not getting applied while using Microsoft Teams. |
| BG-24502 | Microsoft 365 admin center - Resolved an issue where the M365 Admins were unable to access the Users tab in the Microsoft 365 Admin Center Console via reverse proxy. |
| BG-24572 | Gmail - Resolved an issue where users were unable to attach files to emails in Gmail. |
| BG-24594 | Agentless ZTNA Application - Resolved an issue where the landing page of agentless ZTNA application was blank when accessed via reverse proxy. |
| BG-24603 | Multi-Factor Authentication Login Policy - Resolved an issue where the SMS token verification page was not loading properly when a sys/role admin initiates SP/IDP login. |
| BG-24616 | Windows Virtual Desktop - Resolved an issue where users were unable to access Windows Virtual Desktop when its policy Action is set to Secure App Access and Block All File Downloads. |
| BG-24635 |
Web Logs - Resolved an issue where users were unable to:
|
| BG-24701 | Agentless ZTNA Application - Resolved an issue where the images in agentless ZTNA application were not loading when accessed via reverse proxy. |
| BG-24720 | Unmanaged Application Logo - Resolved an issue where the unmanaged application logo was not loading when the Action is set to Coach to a non-predefined managed application with application logo. |
| BG-24733 | API Logs - Resolved an issue where users were intermittently experiencing an error ‘Unable to retrieve results, please contact Forcepoint One support' while trying to access the API Summary/Audit logs. |
| BG-24815 | AWS API Application in FSM - After successfully integrating the Forcepoint ONE CASB system with Forcepoint DLP, the Amazon Web Services (AWS) cloud application, configured in Forcepoint ONE SSE for API scanning, was not available under the page in FSM. Resolved this issue. |
| BG-24959 | Data Security and Data at Rest Dashboards - Resolved an issue where the Data Security and Data at Rest dashboards were not displaying data. |