> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/use-artifact-registry/signing-keys/manage-signing-keys.md).

# Manage signing keys

View, manage status, filter, detach, and delete signing keys in Harness Artifact Registry.

Signing keys enable cryptographic verification of repository metadata for Debian, Alpine, and Wolfi virtual registries in Harness Artifact Registry. Harness signs metadata so package managers can verify the integrity and authenticity of repository contents before installing packages.

Use this guide to view and manage signing keys at the account, organization, or project level. You can change key status, see which registries use each key, and remove keys that are no longer in use.

To review concepts, prerequisites, and status definitions, go to [Signing Keys](https://developer.harness.io/artifact-registry/use-artifact-registry/signing-keys.md).

***

## View signing keys

To view signing keys for your current scope (account, organization, or project), navigate to **Registries Settings** > **Signing Keys**.

The table lists the following columns for each key:

| Column            | Description                            |
| ----------------- | -------------------------------------- |
| **Key Name**      | Unique identifier                      |
| **Type**          | GPG (Debian) or RSA (Alpine and Wolfi) |
| **Algorithm**     | RSA or Ed25519 (GPG only)              |
| **Status**        | Active, Inactive, or Revoked           |
| **Expiration**    | Expiry date or Never                   |
| **Referenced By** | Count of registries using this key     |

Use the filters above the keys list to narrow results by **Key Type** (GPG or RSA) or **Status** (Active, Inactive, or Revoked).

***

## View key details

To open key details, select the specific key name. You can also click **Show more actions** (**⋮**) next to the key, then select **View Details**.

### Summary tab

The Summary tab shows an Overview with the following key properties:

* **Fingerprint (short):** Short fingerprint for quick identification
* **Fingerprint (long):** Longer fingerprint value
* **Fingerprint (full):** Full fingerprint value
* **Key type:** RSA or GPG
* **Source:** How the key was created, such as GENERATED
* **UID:** Unique identifier for the key
* **Expiry:** Expiration date, or Never

The key name and status (Active, Inactive, or Revoked) appear in the page header above the tabs.

### Referenced By tab

The Referenced By tab lists the registries that use this key. Each row includes the following columns:

* **Name:** Registry name
* **Package Type:** Debian, Alpine, or Wolfi
* **Type:** Registry type, such as Artifact Registry
* **Updated:** Time since the registry was last updated

To detach the key from individual registries, use this view.

***

## Change key status

Status controls whether a key signs metadata. To review status definitions and behavior, go to [Key status lifecycle](https://developer.harness.io/artifact-registry/use-artifact-registry/signing-keys.md#key-status-lifecycle).

To change status, perform the following steps:

1. Navigate to **Registries Settings** > **Signing Keys**.
2. Click **Show more actions** (**⋮**) next to the key.
3. Select **Edit**.
4. Select the new **Status** (Active, Inactive, or Revoked).
5. Click **Update**.

### Status transitions

The following table lists the status changes that are allowed for each key status:

| From Status  | Can Change To                    | Cannot Change To            |
| ------------ | -------------------------------- | --------------------------- |
| **Active**   | Inactive, Revoked                | -                           |
| **Inactive** | Active (if not expired), Revoked | -                           |
| **Revoked**  | -                                | Active, Inactive (terminal) |

### Impact on registries

When you change a key status, the change takes effect immediately on every registry that uses the key. The following table lists how each status change affects uploads, metadata, and clients:

| Status Change          | Upload Behavior  | Metadata State   | Client Impact            |
| ---------------------- | ---------------- | ---------------- | ------------------------ |
| **Active → Inactive**  | Uploads continue | Becomes unsigned | Verification warnings    |
| **Active → Revoked**   | Uploads continue | Becomes unsigned | Verification warnings    |
| **Inactive → Active**  | Uploads continue | Becomes signed   | Normal operation         |
| **Inactive → Revoked** | Uploads continue | Remains unsigned | Permanent unsigned state |

{% hint style="warning" %}
**Revoked is permanent**

Revoked status cannot be reversed. Use Revoked when a key is compromised. For a temporary disable, use Inactive.
{% endhint %}

***

## Detach a key

Detaching a key removes the signing association without deleting the key. Uploads continue to work; repository metadata is no longer signed.

### From the registry configuration

To detach a signing key from a registry, perform the following steps:

1. Select the registry in the **Artifact Registry** module.
2. Select the **Configuration** tab.
3. In the **Signing keys** section, select **Edit**.
4. Clear **Signing enabled**.
5. Click **Update**.

### After detachment

Detaching a key has the following effects on the registry:

* New package uploads continue to work.
* Existing packages remain available.
* No new signed metadata is generated.

{% hint style="info" %}
**Differences between Detach and Inactive**

Detach removes the key from the registry. Inactive keeps the key attached but stops using it for signing. Both leave uploads working with unsigned metadata.
{% endhint %}

***

## Delete a key

Delete marks the key as deleted. After deletion, the key cannot be used for any operations.

**Requirements:** The key must be detached from all registries first (**Referenced By** count is 0).

To delete a signing key, perform the following steps:

1. Navigate to **Registries Settings** > **Signing Keys**.
2. Verify the **Referenced By** count is 0.
3. Click **Show more actions** (**⋮**) next to the key.
4. Select **Delete**.
5. Enter the key name to confirm.
6. Select **Confirm**.

{% hint style="warning" %}
**Deletion blocked**

If deletion is blocked, detach the key from all registries first.
{% endhint %}

***

## Troubleshooting

<details>

<summary>Cannot delete a signing key that is still attached to registries</summary>

The error `This key is attached to one or more registries and cannot be deleted` indicates that the key is still in use.

To resolve the error, do the following:

1. Open the key details.
2. Select the **Referenced By** tab.
3. Detach the key from all registries.
4. Retry deletion.

</details>

<details>

<summary>Cannot change a signing key status from Inactive to Active</summary>

The key has expired. Create a new key, attach it to the affected registries, and update client configurations.

</details>

<details>

<summary>Registries show unsigned metadata after a status change</summary>

The key status is Inactive or Revoked.

* **Temporary:** Change the status back to Active.
* **Permanent:** Attach a new Active key.

</details>

<details>

<summary>Cannot detach a signing key from a registry</summary>

Verify you have signing key permissions at the relevant scope (account, organization, or project) and registry-level configuration permissions. Contact your Account Administrator if you need access.

</details>

***

## Next steps

* [Set up signing keys](https://developer.harness.io/artifact-registry/use-artifact-registry/signing-keys/setup-signing.md): Create a key, attach it to a registry, and configure clients.
* [Signing Keys](https://developer.harness.io/artifact-registry/use-artifact-registry/signing-keys.md): Review concepts and status definitions.
* [Configure expiration notifications](https://developer.harness.io/artifact-registry/use-artifact-registry/signing-keys.md#expiration-notifications): Set up expiration alerts.

{% @harness-feedback/feedback %}
