Known Issues In Hotfix Release 119.1.0
Known Issues In Hotfix Release 119.1.0
Here is the list of known issues in this release:
| Issue Number | Category | Description |
|---|---|---|
| 423457 | Netskope Secure Web Gateway (NG SWG) | Rules with filefilter conditions might not be considered when they followed a content inspection rule with a traffic action. |
| 502569 | Netskope Secure Web Gateway (NG SWG) | User and user group match criteria were not applied to SSL Decryption policies for DPoP appliances. |
| 24146 | Remote Browser Isolation (RBI) | A limited number of web sites can reject http requests from RBI due to enhanced connection fingerprinting measures implemented by those sites. |
| 466448 | Traffic Steering | With self protection enabled, when the tokens change in a tenant, the MSIEXEC command (for example, msiexec /I NSClient.msi mode=peruserconfig host= <tenant-name>.goskope.com token=<token ID> enrollauthtoken=<new authentication ID> enrollencryptiontoken=<new encryption ID>) failed to update the tokens while repeating the Client installation using the new tokens. As a workaround, use nsdiag to update the secure enrollment tokens. |
| 438566 | Traffic Steering | Netskope does not support TCP/DNS response handling when DNS responses are received through the tunnel when DNS Security is enabled. |
| 225028 | Traffic Steering | To enable DNS security in web mode, Netskope client tunnel should be re-established. Netskope client detects the DNS traffic enable flag from web UI and then checks for the Cloud Firewall availability on tunnel establishment. If Cloud Firewall is available then the Netskope client starts DNS security. Netskope Client also re-established the tunnel upon machine restart, shutdown, network change and enable/disable of Netskope client. |
