Guidance for Installing 3rd-party Applications on Publishers
Be aware that any additional software (not included with the Netskope provided package) that is installed on a Publisher instance will be sharing resources with the Publisher application. In addition, Netskope and 3rd-party domains and Publisher software processes may need to be whitelisted in the 3rd-party software.
Network security software that monitors each and every action on the Publisher instance may cause performance issues. You can install security software as long as doing so does not impact Publisher performance. It is your responsibility to ensure that enough resources are allocated for all the software applications running on a Publisher instance.
To troubleshoot issues, Netskope Support may request you to test/recreate without 3rd-party software to narrow down the root cause.
Customer-managed Artifact Repositories
Customers may configure Publishers to retrieve software through their own private artifact repositories, mirrors, or caching services. These repositories may be hosted in the customer’s environment or managed through a third-party provider, including Sonatype Nexus Repository, JFrog Artifactory, Cloudsmith, or another artifact repository provider.
For Ubuntu Publishers, this can include delivery of Publisher container images from Docker Hub and operating-system packages from Canonical’s Ubuntu APT repositories.
Netskope also offers an enterprise solution, the Secure Private Artifact Repository for Publishers. This Netskope-controlled service provides operating-system packages and Publisher container images through authenticated repository endpoints. It requires Publisher release R142 or later. Contact your Netskope Account Team to confirm eligibility and request enablement.
Configuration Responsibility and Assistance
Customers are responsible for configuring, maintaining, and troubleshooting their own artifact repositories and the associated settings on their Publishers. Netskope Support does not provide setup assistance or troubleshoot customer-managed repository integrations, including the Docker and Ubuntu APT settings used to connect to those repositories.
Contact the selected artifact repository vendor for assistance with:
- Configuring Docker Hub proxying or mirroring and Ubuntu APT repository proxying or mirroring.
- Applying the appropriate Docker and APT client settings on an Ubuntu machine.
- Configuring authentication, TLS certificates, and repository signing-key trust.
- Ensuring required images, packages, dependencies, and current repository metadata remain available for manual and automatic updates.
Use the vendor’s documentation and support service for the chosen product and deployment. The following references provide starting points:
| Provider | Documentation |
|---|---|
| Sonatype Nexus Repository | Docker proxy repositories and APT repositories |
| JFrog Artifactory | Docker repository setup and Debian/Ubuntu repositories |
| Cloudsmith | Docker Hub integration and upstream proxying and caching, including Debian/Ubuntu packages |
For underlying client behavior, refer to Docker’s registry mirror documentation and Canonical’s Ubuntu package-management documentation.
Troubleshooting Failed Updates
If a Publisher software or operating-system update fails, Netskope Support may ask the customer to temporarily disable or bypass the customer-managed artifact delivery integration, restore the applicable Netskope-documented software delivery configuration, and retry the update. The customer is responsible for making these changes and providing the necessary network access to the applicable software sources.
This test helps determine whether the customer-managed repository or its configuration contributes to the failure. If the issue is isolated to that integration, contact the artifact repository vendor for assistance. Netskope Support continues to support the Publisher within the scope of the Publisher Support Policy.
This troubleshooting request concerns the customer-managed delivery layer. Keep software authenticity verification enabled and retain the requirements of the Netskope Secure Private Artifact Repository when that service is enabled.