Bug Fixes

This release of the product includes these general bug fixes.

General

ID Description
BG-19482 Agentless ZTNA - When using Agentless ZTNA with non-standard HTTP/S port numbers, the port number is set in the HTTP Host header towards the server.
BG-20131 Azure DevOps Wikis - Resolved an issue where users were getting 400 error while saving updates to Azure DevOps Wiki pages with the SmartEdge agent installed.
BG-20435 Google Drive API - Resolved an issue where Google Drive API scanning was happening for a user not in the configured group.
BG-20475 Google API Actor Field value - Removes spurious escape character “\” added before a dot (.) in the actor field while saving policies.
BG-20481 Web and Web DLP Logs - Managed applications logs are no longer incorrectly displayed under the Web and Web DLP logs instead of the Proxy logs when SWG license is not enabled.
BG-20585 Workday Drive - Users are now able to access Drive from Workday via reverse proxy.
BG-20882 Web Log - Resolved an issue where the Web log page was not displaying any results when set to default filter Action=Denied.
BG-20978 Microsoft 365 in Reverse Proxy - Resolved an issue where the Microsoft 365 Compliance center application fails to load with an error while accessing it via reverse proxy.
BG-21020 API Scan - When customer initiate DropBox or OneDrive API scanning, the files older than two weeks were showing Pending DLP Scan. Resolved this issue.
BG-21166 Agentless ZTNA - When using Agentless ZTNA application with non-standard HTTP/S port numbers, the port number is removed from the location field in the HTTP response received from server.
BG-21185 Cloud SWG - Resolved an issue where anonymous user creation was getting failed for Cloud SWG in non-primary regions.
BG-21243 ACS Proxy - Resolved an issue where ACS Proxy login was not working if SAML destination is workplace.com in reverse proxy.
BG-21296 Forward proxy auth - Resolved an issue where fwd_proxy_auth does not fall back to primary region correctly.
BG-21319 HTTP/HTTPs ZTNA - Users can now use high port numbers while configuring HTTP/HTTPs ZTNA application.