PUT SSH Keys My Key
PUT SSH Keys My Key
The PUT /SSH The SSH (secure shell) protocol provides for secure connections between computers. It provides several options for authentication, including public key, and protects the communications with strong encryption./Keys/MyKey method is used to update the existing SSH key pair
In asymmetric cryptography, public keys are used together in a key pair with a private key. The private key is retained by the key's creator while the public key is widely distributed to any user or target needing to interact with the holder of the private key. for the current user in Keyfactor Command. Most features of a key pair are fixed and cannot be changed. Only the email address and comment associated with the key may be changed with this option. This method returns HTTP 200 OK on a success with the key's details.
Table 491: PUT SSH Keys My Key Input Parameters
Name | In | Description |
---|---|---|
ID | Body | Required. The Keyfactor Command reference ID for the SSH key. |
Body | Required. A string containing the email address of the user who requested the key. This email address is used to alert the user when the key pair is approaching the end of its lifetime. | |
Comment | Body | An array containing one or more strings with the user-defined descriptive comments, if any, on the key. Although entry of an email address in the comment field of an SSH key is traditional, this is not a required format. The comment may can contain any characters supported for string fields, including spaces and most punctuation marks. Note: Although this field is actually an array, entry of only a single comment string is supported. The field is defined as an array to support multiple comments on existing SSH keys found on servers during inventory and discovery. |
Table 492: PUT SSH Keys My Key Response Data
Name | Description |
---|---|
ID | The Keyfactor Command reference ID for the user's SSH key pair. |
Fingerprint |
A string indicating the fingerprint of the public key. Each SSH public key has a single cryptographic fingerprint that can be used to uniquely identify the key. |
PublicKey | A string indicating the public key of the key pair. |
KeyType |
A string indicating the cryptographic algorithm used to generate the SSH key pair. Possible values are:
|
KeyLength | An integer indicating the key length for the SSH key. The key length supported depends on the key type selected. Keyfactor Command supports 256 bits for Ed25519 and ECDSA and 2048 or 4096 bits for RSA. |
CreationDate | The date, in UTC, on which the SSH key pair was created. |
StaleDate |
The date, in UTC, on which the SSH key pair will be considered to have reached the end of its lifetime. By default, the lifetime of an SSH key pair is 365 days. The SSH lifetime is defined by the Key Lifetime (days) application setting. See Application Settings: SSH Tab in the Keyfactor Command Reference Guide for more information. |
A string containing the email address of the user who requested the key. This email address is used to alert the user when the key pair is approaching the end of its lifetime. | |
Comments | An array containing one or more strings with the user-defined descriptive comments, if any, on the key. Although entry of an email address in the comment field of an SSH key is traditional, this is not a required format. The comment may can contain any characters supported for string fields, including spaces and most punctuation marks. Keys created through the Keyfactor Command My SSH Key portal or with the POST /SSH/Keys/MyKey method will contain only one string in the array. |
LogonCount | An integer indicating the number of Linux logons associated with the SSH key pair. |
