Private Access Cloud

The Private Access Cloud known issues in this release are:

Issue Number

Description

910653

When Latency-based (GSLB) Local Broker Selection for Publishers is enabled and the DNS Hostname field is empty, Publishers set to connect to Local Broker connect incorrectly to the Cloud NPA Publisher Gateway (Stitcher) instead of a Local Broker Publisher Gateway (Stitcher). The tenant UI incorrectly shows the Publisher as Local Broker: Connected because it connects to the Cloud NPA Publisher Gateway (Stitcher).

Workaround: Enter any valid FQDN or placeholder hostname in the DNS Hostname field in the tenant UI. This issue will be fixed in R138, and the workaround will no longer be needed..

Publisher

The Publisher known issues in this release are:

Issue Number

Description

1001605

After upgrading the NPA publisher on RHEL to latest version, the Publisher wizard may show:
Unable to determine publisher update status; perform publisher update to reset state.
even though the Publisher is current.
Impact: The message is misleading; there is no functional impact.
When it happens: Usually appears after an upgrade when using an existing terminal session.
Workaround: Open a new terminal session on the publisher host and rerun the publisher wizard. The correct status will appear..

Netskope Private Access Release Notes Version 137.0

Netskope Private Access Release Notes Version 137.0