Known Issues In Release 120.0.0
Known Issues In Release 120.0.0
Here is the list of known issues in this release.
Issue Number | Category | Description |
---|---|---|
466448 | Traffic Steering | With self protection enabled, when the Secure Enrollment 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 DNS over TCP response handling when DNS responses are received through the tunnel when DNS Security is enabled. |
525134 | Traffic Steering | The error message displayed for the Minimum OS Version in Device Classification is not consistent and descriptive enough for users. The error message must include the OS version format. Additionally, there is no maximum character limit in the input field. |
531035 | Netskope Private Access (NPA) | In scenarios where the AnyApp beta feature (with Publisher release 119 or earlier) is enabled, and when upgrading from Publisher release 119 or earlier to 120, the Browser Access AnyApp components cannot be upgraded along with the Publisher. The workaround is to re-enable the Browser Access AnyApp feature via the Publisher wizard after upgrading the Publisher. |