Skip to main content
Connect your package registry so ZeroPath can resolve internal libraries and the dependencies they bring into your application. Use this setup when a Maven, Gradle, or sbt build needs private packages, parent POMs, BOMs, or build plugins.

Choose the connection

In Settings → Integrations → Registries → Package registries, choose: Connections apply to the organization. You can save one Maven / Gradle connection and one sbt connection. If you scan both build types, configure both connections, even when they use the same registry and account.

Before you connect

  • You need the Create Integrations permission.
  • Use a dedicated account or token with read access to the packages and build plugins your projects need.
  • Get the HTTPS URL of a virtual or group repository that serves your internal packages and proxies their public dependencies. Use the repository endpoint, such as https://mycorp.jfrog.io/artifactory/maven-virtual/ or https://nexus.example.com/repository/maven-public/, rather than the registry’s sign-in page. Native Maven resolution routes all repositories through this URL.
  • Choose a published private package whose POM requires authentication. You will need its exact group:artifact:version, for example com.example:shared-library:1.2.3.
  • For hosted ZeroPath, the registry must be reachable over the public internet; private-network addresses are rejected. A self-hosted ZeroPath instance can use registries on its private network. HTTPS is still required, and loopback and cloud-metadata addresses remain blocked.

Connect Maven or Gradle

1

Open Package registries

Open Settings → Integrations. Select Add Integration → Registries, then find Maven / Gradle under Package registries and click Connect.
2

Enter the repository and credentials

Set Registry URL to your virtual or group repository URL.For Basic, enter Username and Password / identity token. For Bearer token, enter the token without a username. If your Gradle build reads .artifactory_credentials, ARTIFACTORY_USERNAME, or ARTIFACTORY_PASSWORD, choose Basic so those values are available during build setup. Store the secret in this form, not in your repository or URL.
3

Verify a private package

In Private package to verify, enter group:artifact:version for a published private package, then click Connect registry. ZeroPath checks that the package requires authentication and that its POM is readable with your credentials. Directory listing is not required.For com.example:shared-library:1.2.3, the POM must be available at com/example/shared-library/1.2.3/shared-library-1.2.3.pom beneath the repository URL. A JAR without a POM is not enough for this check.
The connection supplies credentials for Maven POM/BOM lookups and native Maven and Gradle dependency resolution. It also supports Gradle build setup that reads the Artifactory credentials file or environment variables listed above.

Private Gradle plugins

Declare the private plugin repository in pluginManagement.repositories in settings.gradle or settings.gradle.kts. A repository declared only in a project’s repositories block does not configure plugin resolution. For example, in settings.gradle.kts:
ZeroPath supplies authentication to Maven repositories on the connected host, including declared plugin repositories. The repository must contain the plugin and any metadata it needs; a successful library POM check does not verify plugin access.

Connect sbt

Under Package registries, click Connect for sbt (Scala / Java) and complete these fields: Click Connect registry. ZeroPath verifies the private POM and, if supplied, the Ivy metadata file. Ask your registry administrator for the exact Ivy path; it is not a Maven coordinate or a directory listing. Credentials are available before sbt starts and loads its build definition, including private meta-build dependencies and plugins. Ivy, Coursier, and builds that read .artifactory_credentials or ARTIFACTORY_USERNAME / ARTIFACTORY_PASSWORD can use the connection. You do not need to commit these credentials to your project.

Run a scan and check coverage

After connecting, run a new full scan or SCA scan of the affected repository. Saved connections are used automatically; previous scan results are not updated.
  1. In Assets → Repositories, open the repository. Select the scanned branch in Inventory and check manifest resolution under Overview.
  2. In Inventory → Dependencies, check for a known internal library and one of its expected transitive dependencies, including their resolved versions.
  3. If the scan fails, read its error. For incomplete coverage, see how to retrieve manifest warnings and check registry access and build configuration before retrying.
Connected confirms access to the package used for verification. The scan checks the rest of the build and its transitive dependencies.
Gradle and sbt can resolve transitives with their native build tools or a supported committed lockfile: gradle.lockfile, build.sbt.lock, or lock.sbt. To avoid running the build during scanning, generate the lockfile in your build environment with registry access and commit it. When the manifest resolves from that lockfile, ZeroPath skips native build resolution. See lockfile setup and commands. If the scan reports an error with a saved registry connection, correct it before retrying.
For Maven packages published only to private repositories, some transitive dependencies may remain unresolved after connecting. Check the scan’s coverage and contact support with the scan URL and affected package coordinates if expected dependencies are missing.

Troubleshooting

If the warning persists, send support the scan URL, affected manifest path, warning message, and a package coordinate you expected to resolve. Do not include tokens or passwords. To rotate credentials, Edit the connection and save the new secret. Leaving the secret field blank keeps the existing one; changing the authentication mode requires a new secret. Changes apply to subsequent scans across the organization.