Adding a public or private key to a keyset

You can add both public and private keys to a keyset using SSH Protect.

To add a public or private key

From the SSH Protect menu, click SSH Keys.
Locate the keyset to which you want to add a public or private key instance.

For more information, see Finding SSH assets using filters.

From the Keyset Details page, click Add New.

NOTE If you don't see the Add New button, verify you have proper permissions to add a key.

Field Descriptions for Private keys tab

NOTE This table is sorted by Field Name.

Field Name	Description
Account	A free-text field where you can enter the account name on the operating system account that the key is created for. This account name is displayed in the key details. You can use this value for filtering keys tied to a particular user's account. Object names may not contain the backslash `\` or less-than sign `<` characters. Object names (including their path ancestors in the policy tree) must be fewer than 255 total characters.
Add Keyset to Folder	The policy folder where the keyset will be added. If your account has the correct permissions on a device this field is optional. However, application owners who do not have permissions on a device can add the keyset to a policy folder, and SSH Protect can push the keys to the device. This is a self-service feature that lets application owners to add keys to a device without requiring the application owner to have permissions on the actual device itself. If the user does not have the correct permissions to create the key on the device itself, then this field is required. For more information, see Creating a new keyset as an application owner.
Add to this Device	A reference field to the device that the key is linked to. The device must already exist in the database before you can select it here.
Deny From	Enter specific hosts that are not allowed to connect using this public key.
Forced Command	Enter the command to run with this key.
Format	The key format. Options are OpenSSH, SSH2 (Tectia), and PuTTY. For more information about SSH2, see Support for SSH Tectia 4.x, 5.x, and 6.x
Key Path	Path where the key is stored, including the key name. For example, /home/alice/.ssh/id_rsa.
Key Type	Select if this is a host or a client key type.
Passphrase	An optional level of security you can add to protect the keyset.

Field Descriptions for Authorized keys tab

NOTE This table is sorted by Field Name.

Field Name	Description
Account	A free-text field where you can enter the account name on the operating system account that the key is created for. This account name is displayed in the key details. You can use this value for filtering keys tied to a particular user's account. Object names may not contain the backslash `\` or less-than sign `<` characters. Object names (including their path ancestors in the policy tree) must be fewer than 255 total characters.
Add Keyset to Folder	The policy folder where the keyset will be added. If your account has the correct permissions on a device this field is optional. However, application owners who do not have permissions on a device can add the keyset to a policy folder, and SSH Protect can push the keys to the device. This is a self-service feature that lets application owners to add keys to a device without requiring the application owner to have permissions on the actual device itself. If the user does not have the correct permissions to create the key on the device itself, then this field is required. For more information, see Creating a new keyset as an application owner.
Add to this Device	A reference field to the device that the key is linked to. The device must already exist in the database before you can select it here.
Allow From	Enter specific hosts that are allowed to connect using this public key.
Deny From	Enter specific hosts that are not allowed to connect using this public key.
Forced Command	Enter the command to run with this key.
Format	The key format. Options are OpenSSH, SSH2 (Tectia), and PuTTY. For more information about SSH2, see Support for SSH Tectia 4.x, 5.x, and 6.x
Key Path (Existing)	Path where the key is stored. Use the drop-down to select a key path from the AuthorizedKeyFile. If the key path isn't listed, click Add New to switch this field to allow you to enter a new key path.
Key Path (New)	Path where the key is stored, including the key name. For example, /home/alice/.ssh/id_rsa. If you want to select a key path specified by the AuthorizedKeyFile, click Select Existing.
Key Type	Select if this is a server or a client key type.
Options	Additional options you can set for the authorized key.
Passphrase	An optional level of security you can add to protect the keyset.

To add a new OpenSSH key, choose OpenSSH in the Format field, and then select its Options.
To add a new Tectia key, choose SSH2 (Tectia) in the Format field, and then select its Options.
Specify Allow From, Deny From, and Forced Commands, as needed.
When you're done, click Save.