Skip to main content

Netskope Help

Known Issues In Release 97.0.0

Here is the list of known issues in this release.

Issue Number

Category

Description

193306

Netskope Secure Web Gateway (NG SWG)

Currently, the proxy swaps the host URL-based app name with the referrer-based app name. Policy lookup occurs based on the referrer app name.

There are few exceptions where the app name is not swapped:

  • If both host referrers belong to the same app group (such as Gmail and Google Chat).

  • If the referrer category is IdP. (The category is from hash_domains.json, which is part of the content package.)

  • If the referrer doesn’t have a connector.

  • If the referrer is unmanaged.

To ensure that the app name isn’t swapped, you can use the following configuration and provide the app name or domain. For example:

"telemetry-app-swap-exception": {
2         "apps": [
3            "Microsoft Office365"
4           ],
5           "domains": [
6            "login.microsoftonline.com"
7           ]
8   }

If the above configuration is pushed through the provisioner API, the app name swap doesn’t occur for the traffic where the referrer app is Microsoft Office365 or the domain is login.microsoftonline.com".

Use the following API to push the configuration:

curl -v -H 'Content-Type: application/json' -d '{"telemetry-app-swap-exception":{"apps": [<appname>]}}' http://provisionervip:6400/dp/config/sync?tenantid=<tenantid>