Skip to main content

​
Overview

OneCLI routes your agents’ package installs through your own JFrog Artifactory, using an access token. Agents pull npm, PyPI, and other packages from your approved remote repositories, and the gateway injects the token so your agent never sees it. Connecting takes about a minute.

​
Connect JFrog Artifactory

1

Create an access token in JFrog

In the JFrog Platform, open Administration > User Management > Access Tokens and click Generate Token. Give it read and deploy on the remote repositories agents should use, and copy it right away.
2

Enter it in OneCLI

In the OneCLI dashboard, open Connections > JFrog Artifactory and fill in:
  • Access Token: the token you copied.
  • JFrog Host: your host, for example mycompany.jfrog.io.
Click Connect JFrog Artifactory.
OneCLI connect window for JFrog Artifactory, showing the setup guide link, the Access Token and JFrog Host fields, and the Connect JFrog Artifactory button.

The JFrog Artifactory connect window in OneCLI.

OneCLI doesn’t test the token when you connect. A wrong token or host shows up on the agent’s first package install.

​
What it changes for agents

When JFrog is connected, OneCLI blocks the public npm registry (registry.npmjs.org) and PyPI (pypi.org) by default, so installs go through your Artifactory. You can change these blocks under Connections > JFrog Artifactory.

​
Controlling access

Grant the connection to each agent that needs it. Organization rules add guardrails on top. A blocked request never reaches JFrog. To disconnect, remove the connection in Connections > JFrog Artifactory, then revoke the token in JFrog under Access Tokens.