> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/miscellaneous-integrations/private-registries/jfrog-artifactory.md).

# JFrog Artifactory

Use Aikido Registry Proxy as the default upstream for Artifactory, so every package your team installs is checked for malware, age restrictions, and known vulnerabilities. Additionally this allows you to install [Aikido Libraries](/autofix-and-remediation/aikido-libraries-overview.md) directly from your Artifactory.

{% stepper %}
{% step %}

### Get your Aikido proxy URL

Go to [Settings > Registry Proxy](https://app.aikido.dev/issues/aikido-libraries/setup-instructions), select your ecosystem and copy the upstream proxy URL

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-d8af4ae912800a6d829193833ff1c9c9aa8635af%2FScreenshot%202026-08-11%20at%2009.34.58.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Create a Remote Repository in Artifactory

1. In Artifactory, go to **Administration > Repositories**.
2. Click **New Repository** and select **Remote**.
3. Set **Package Type**
4. Give the repository a key, for example `aikido`.
5. Set the **URL** field to your Aikido proxy URL from step 1.
6. Save the repository.

{% hint style="info" %}
If packages don't reflect the latest data from Aikido, set the **Metadata Cache Lifetime** to `0` in the remote repository settings. This forces Artifactory to always fetch fresh metadata from the Aikido proxy instead of serving a cached version.
{% endhint %}
{% endstep %}

{% step %}

### (Optional) Create a Virtual Repository

If you also have internal packages stored in a local Artifactory repository, create a Virtual Repository that aggregates both:

1. Go to **Administration > Repositories > New Repository > Virtual**.
2. Set **Package Type** to match your remote repository
3. Add your local repository and the remote repository as members.
4. Point your package manager at the virtual repository URL instead.

This gives your team a single registry endpoint that serves both internal packages and externally proxied packages through Aikido.
{% endstep %}

{% step %}

### Configure Developer Machines to use Artifactory

Point each developer's package manager at the Artifactory repository. See JFrog's documentation for the exact steps:

{% tabs %}
{% tab title="npm" %}
[npm repositories - connect your client](https://docs.jfrog.com/artifactory/docs/npm-repositories#connect-your-npm-client-to-artifactory)
{% endtab %}

{% tab title="PyPI" %}
[PyPI repositories - connect your client](https://docs.jfrog.com/artifactory/docs/pypi-repositories#connect-your-pypi-client-to-artifactory)
{% endtab %}

{% tab title="Maven" %}
[Maven repositories - connect your client](https://docs.jfrog.com/artifactory/docs/maven-repositories#connect-your-maven-client-to-artifactory)
{% endtab %}

{% tab title="NuGet" %}
[NuGet repositories - connect your client](https://docs.jfrog.com/artifactory/docs/nuget-repositories#connect-your-nuget-client-to-artifactory)
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### (Optional) Block the public registry with Device Protection

Once Artifactory is in place, developers can still bypass it by pointing their package manager directly at the public registry. Deploy Aikido Device Protection to enforce that all traffic goes through your private registry.

{% content-ref url="/pages/sa7N9YXthBxZbm6WmKBq" %}
[Block Public Package Registries](/aikido-device-protection/using-aikido-endpoint/block-public-package-registries.md)
{% endcontent-ref %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/miscellaneous-integrations/private-registries/jfrog-artifactory.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.