> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/configuring-your-jfrog-artifactory-container-registry-integration.md).

# Configuring your JFrog Artifactory Container Registry integration

How to configure the Snyk JFrog Artifactory Container Registry integration

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Configuring your JFrog Artifactory Container Registry integration

The instructions on this page explain how to enable integration between one Artifactory instance as a container registry and a Snyk Organization to start managing your image security.

### Prerequisites for Artifactory Container Registry integration

* You must be an administrator for the Organization you are configuring in Snyk.
* You must provide user credentials to integrate with Artifactory.
* You must be running Docker. Snyk supports Docker repositories and the Docker package type for this integration.
* If you are using a self-hosted Artifactory instance, see [Snyk Broker - Container Registry Agent](https://docs.snyk.io/platform-administration/snyk-broker/snyk-broker-container-registry-agent).

### Configure Artifactory Container Registry integration

1. Log in to [your Snyk account](https://app.snyk.io).
2. Navigate to **Integrations**. From the list of integrations, select **Artifactory.**\
   The configuration page opens.
3. Enter your credentials:
   * **Username and Password -** use your Artifactory login credentials. If you're using SSO configuration, you must generate an access token in Artifactory and use the token details to login.
   * **Container registry name -** the full registry URL: `<subdomain>.jfrog.io/artifactory/api/docker/<repo-name>`

<figure><img src="https://user-images.githubusercontent.com/112600/144875482-078b715e-2834-469b-9983-7e88a65f175e.png" alt="Artifactory account credentials" width="375"><figcaption><p>Artifactory account credentials</p></figcaption></figure>

4. Click **Save Changes**. A confirmation appears.

{% hint style="info" %}
To set up the integration, the Artifactory credentials need, at minimum, read permissions to the relevant Artifactory repository.
{% endhint %}

Snyk tests the connection values and the page reloads, now displaying integration details as you entered them. At the top of the screen, a confirmation message indicates that the details were saved. If the connection fails, a notification appears.


---

# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/configuring-your-jfrog-artifactory-container-registry-integration.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.