> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrating-registry-in-delivery-shield/nexus-artifact-registry.md).

# Nexus Artifact Registry

Nexus is a repository manager from Sonatype that stores and serves build artifacts (JARs, Docker images, npm/PyPI packages), and in Delivery Shield it acts as the trusted artifact source that pipelines pull from and push to, so artifacts can be verified, scanned, and policy-checked before they are promoted toward deployment.

### Usage of Nexus Artifact Registry in Delivery Shield:

* Delivery Shield gets notified for every build run in a pipeline. To identify the artifact for every build, it connects to the Nexus repository and pulls the newly built artifact.
* Once the artifact is pulled, it runs security scans on it. The scanned results are available in the Vulnerability Management page and the Artifact section of the DBOM page.

### To Integrate Nexus Artifact Registry:

1. Navigate to **Setup** > **Integrations**.
2. Click the Artifact tab. In the artifacts that appear, click **Nexus Artifact Registry**.

<figure><img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2FekDM2h3lyG57BBIo2Rpt%2Fnexus%201.png?alt=media&amp;token=d23be53a-153a-470c-8df5-3424532b8b30" alt=""><figcaption></figcaption></figure>

The integration page is displayed. Click **+New Account**.

<figure><img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2FtmXuMcYvhjEUTxJZ9jrs%2Fimage.png?alt=media&amp;token=5ccb7e6a-dc45-4f97-a112-fb52dc287de6" alt=""><figcaption></figcaption></figure>

3. In the popup that appears, enter the details for the following:

* **Account Name** - The name of the user account.
* **Host Url** - The host Url link.
* **Auth Type -** Password or Token
  * **Username** - The username to access the account.
  * **Password** - The password to access the account.
  * **Token** - The token to access the account.&#x20;
* Select the **Teams** and the corresponding **Environments** from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.&#x20;

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can select up to 5 teams for the integration to be displayed. </p></div>

  * An example is given below for reference:

  <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuMZQzZsZQuulVdW9B9OuffNPoEXqbcpcAkYtKVyb7YiTQxbVIt1L4Gh-zshqX2J9MFKIat8x4oWFIGxdg3j1XVagyUNhUAlD_52soyMyd1cy53p6XiYi0LsTjIBfHcybRWl61?key=D9EXoOdGF7oYOBvYaW2GnRWJ" alt=""><figcaption></figcaption></figure>

  * In the example above,&#x20;
    * if **Team 1**, **Team 2**, and **Team 3** are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as **Team 4**, will not have access to this account.
    * Even if the user who created this account is also an admin for **Team 4**, the integration account remains restricted and is not available for **Team 4**.&#x20;
    * Access to the account is strictly limited to the specified **Teams** and **Environments** selected during account creation.
  * **For Organization Admins:**
    * When an **Organization Admin** creates an account without selecting specific **Teams** and **Environments**, the account will be universally applicable, granting access to **all teams** and **all environments** by default.
  * **For Team Admins with Multiple Teams:**
    * If a **Team Admin** who manages multiple teams creates an account without specifying particular **Teams** and **Environments**, the account will only be accessible to the teams for which the logged-in user holds admin privileges.

5. Click **Test** to check if the entered values are valid. If the given values are valid, a popup appears at the top as shown below indicating it.&#x20;
6. Once validated, click **Save**. The Nexus Artifact Registry  account gets integrated in the artifact stage.
7. To edit the entered values, click on the three dots provided in the **Actions** column. In the dropdown select **Edit**.
8. Re-enter the new values and click Update.

The new values get updated.

<br>
