> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/get-started/connect-your-environment/jfrog.md).

# JFrog Artifactory

Give Konvu read access to private packages in JFrog Artifactory.

Connect JFrog Artifactory so Konvu can read private dependencies during assessments and when preparing fix pull requests. Konvu supports npm, Maven and PyPI repositories. This connection supplies package access; it does not import JFrog Xray findings or publish packages.

Connections belong to your Konvu organization. You choose which Artifactory repositories to connect, and Konvu creates a separate connection for each selection. Connect the application through [source code analysis](https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code.md) as well.

## Prerequisites

* Your Artifactory instance's HTTPS base URL, for example `https://acme.jfrog.io`.
* A JFrog identity or access token that can read the repositories and packages your applications need. Konvu does not need an administrator token.
* Network access from Konvu to your Artifactory instance. If your instance restricts access by IP, check its allowlist with your Artifactory administrator.

To create an identity token in JFrog, open your profile menu, select **Edit Profile**, then **Generate an Identity Token**. Identity tokens use their owner's permissions. See [JFrog's identity token guide](https://docs.jfrog.com/user-management/docs/identity-tokens) and [repository permissions](https://docs.jfrog.com/administration/docs/permissions).

## Connect repositories

1. Open **Integrations > JFrog** in Konvu.
2. Enter your instance URL in **Artifactory base URL**. Use the instance URL, not a package repository endpoint.
3. Paste your token into **Access token**.
4. Click **Find repositories**.

<figure><img src="https://4216786002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd2uS6kuROSFKDrT5HC1U%2Fuploads%2Fgit-blob-7e2cfac4c2d21c9ab64371df139420815580187e%2FJFrog%20Artifactory%20setup.png?alt=media" alt="JFrog setup with a fictional acme Artifactory URL and a masked dummy access token" width="600"><figcaption><p>Enter your Artifactory instance URL and access token. The URL and masked token in this example are fictional.</p></figcaption></figure>

5. Select the repositories your applications use. Check the **Repository**, **Ecosystem** and **Type** columns.
6. Click **Connect**, which shows the number of selected repositories.

<figure><img src="https://4216786002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd2uS6kuROSFKDrT5HC1U%2Fuploads%2Fgit-blob-8bf00c5df85ac00079affc2f9df71e3d4102d742%2FJFrog%20Artifactory%20repositories.png?alt=media" alt="JFrog repository selection with fictional Maven, npm and PyPI virtual repositories selected" width="600"><figcaption><p>Select the repositories your applications need. The Maven, npm and PyPI repository names in this example are fictional.</p></figcaption></figure>

Konvu builds the package registry URLs from your selections. If your applications use a virtual repository that combines private packages and upstream dependencies, select that repository.

{% hint style="info" %}
Repository discovery lists the repositories visible to your token. It does not prove that every dependency can be downloaded. JFrog permissions must allow access to the package paths your applications need.
{% endhint %}

### Enter a Maven repository manually

If you already know the Maven resolution endpoint, click **Enter a repository URL manually**. Enter **Repository URL**, for example `https://acme.jfrog.io/artifactory/libs-release/`, and **Access token**, then click **Connect**. This manual option connects one Maven repository.

## Verify package access

Run an assessment for a finding in an application that uses the connected repositories. Confirm that the repository is included in your [assessment settings](https://docs.konvu.com/konvu/administration/assessment-settings.md). Connecting Artifactory alone does not start an assessment.

## Troubleshooting

| Problem                                          | What to check                                                                                                            |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| JFrog rejects the token                          | Check that it is active, unexpired and has the required repository permissions.                                          |
| No repositories appear                           | Check the token owner's repository permissions and permission targets in JFrog.                                          |
| Konvu cannot reach Artifactory                   | Check the HTTPS base URL, network access and any IP allowlist.                                                           |
| Discovery succeeds, but a package download fails | Check access to the specific package path and that the selected repositories contain or proxy all required dependencies. |

Next, [read an assessment](https://docs.konvu.com/konvu/triage-and-remediation/exploitability-assessment/reading-an-assessment.md) or [prepare a fix pull request](https://docs.konvu.com/konvu/triage-and-remediation/remediate/fix-pull-requests.md).


---

# 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://docs.konvu.com/konvu/get-started/connect-your-environment/jfrog.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.
