---
title: "SSH Keys tab"
slug: "ng-29894-dtagauthenticatewiththeirownsshkeysontheiracsdevicesdoc"
updated: 2026-06-24T14:19:52Z
published: 2026-06-24T14:19:58Z
canonical: "docs.zpesystems.com/ng-29894-dtagauthenticatewiththeirownsshkeysontheiracsdevicesdoc"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zpesystems.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SSH Keys tab

The SSH Key-Pair Management capability enables administrators to centrally manage and use SSH key-based authentication when accessing managed devices through Nodegrid.

This feature provides a secure and flexible alternative to password-based authentication by allowing administrators to upload, store, and assign SSH key-pairs to one or more managed devices.

#### General Considerations

- **Ensure** that the public SSH key is installed on the managed device (it is possible to do it manually with ssh-copy-id command), the system **does not** do this automatically when assigning the SSH key under managed device drilldown page.
- This feature **does not** support import/export settings.
- Running the import_settings routine for a managed device that has an SSH key assigned to it will **not work** if the SSH key **doesn’t exist** on Nodegrid.
- The registered SSH key-pairs **are not** user/group restricted for usage, if an admin uploads a key-pair and assigns it to a device, a user with managed device permissions **will** access it using that SSH key.
- If FIPS 140-3 mode is enabled, the **RSA 1024** algorithm option will **not** be displayed on the SSH key type selection field when generating a new key.
- **Deprecated** API endpoints:
  - GET /api/v1/devices/table/<device>/sshkeys
  - POST /api/v1/devices/table/<device>/sshkeys/generate
  - POST /api/v1/devices/table/<device>/sshkeys/send

### Creating an SSH key entry

1. Navigate to *SECURITY::SSH KEYS*

![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-0M87UDNP.png)
2. Click **Add**

![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-BP5VJDC7.png)
3. Enter the **Name** (required if not uploading key file)
4. Enter a **Comment** (optional)
5. Under **Private Key**, select one of the following options:
  1. **Generate Key**
    1. Select the **SSH Key Type** from the drop-down menu![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-K8H2LJXW.png)
  2. **Local Computer**
    1. Click **Choose File** to upload a private key file from the local machine
    2. Select the **Password protected SSH key** checkbox if the key is password protected, and fill-in the **Password** field

![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-83XK7K53.png)
  3. **Text Input**
    1. Paste the private key content in the text area (OpenSSH format)

![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-LFA2ZL4F.png)
6. Click **Save**

### Editing an SSH key entry

1. Navigate to *SECURITY::SSH KEYS*
2. Select the SSH key

Only the **Comment** field can be edited
3. Click **Save**

![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-S9Q7HL7Y.png)

### Assigning an SSH key to a managed device console access

1. Navigate to *MANAGED DEVICES::DEVICES*
2. Select the device to assign the SSH key, or create one
3. Select the **Allow Pre-shared SSH Key** checkbox
4. Select the existing SSH Key from the drop-down menu![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-MFMF7Q87.png)
5. Click **Save**

> [!WARNING]
> Note
> 
> The user has to manually send the SSH public key to the selected managed device, since the system does not do this automatically.
> 
> 
> 
> It is possible to do this is going to the root shell and running `ssh-copy-id -i /etc/devices_keys/key_pairs/{key-name}.pub {user}@{device_ip}.`
> 
> After running the code, it is possible to perform a console access using the SSH Key (If the device status is "Enabled", make sure to close the current connection and open a new one to force usage of SSH key).

### Assigning an SSH key to auto-discovery management

1. Navigate to *MANAGED DEVICES::DEVICES*
2. Select the device to assign the SSH key, or create one
3. Go to the **Management** tab
4. Select the **SSH/Telnet** checkbox under **Protocol**
5. On **Credential**, select the **Use Specific** option
6. Select the **Allow Pre-shared SSH Key** checkbox, a drop-down menu will be displayed with the existing SSH Keys

![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-T1HC2DUM.png)
7. Click **Save**

> [!NOTE]
> Note
> 
> Given that your discovery rules are configured correctly, when the discovery is executed and it creates new children managed devices, they should inherit the access configuration from the parent, including the SSH key assigned, if any.

### Reset SSH fingerprint

1. Navigate to *MANAGED DEVICES::DEVICES*
2. Select the device to Reset SSH Fingerprint
3. Click the **Reset SSH Fingerprint** button

A confirmation pop-up is displayed
4. click **OK**

> [!WARNING]
> Note
> 
> The button is only displayed if the managed device IP Address is present on the /etc/devices_keys/known_hosts file.

![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-0SOM5Y0W.png)

> [!NOTE]
> Note
> 
> The next SSH connection done to this device (either via console access or auto-discovery) will automatically add the new SSH fingerprint to the known_hosts file.