SSH Key Management

This page is available only in HTTPS mode. This page can used to 'update' public key and private key. There are current following two File Uploads

• Public Key File Upload
• Private Key File Upload.

Key Pair - Public and Private

• Key Pair - Public and Private - In the SSH public key authentication use case, it is rather typical that the users create (i.e. provision) the key pair for themselves. SSH implementations include easily usable utilities for this (for more information see ssh-keygen)
• A public key that is copied to the SSH server(s). - Anyone with a copy of the public key can encrypt data which can then only be read by the person who holds the corresponding private key. Once an SSH server receives a public key from a user and considers the key trustworthy, the server marks the key as authorized in its authorized_keys file. Such keys are called authorized keys.
• A private key that remains (only) with the user. - The possession of this key is proof of the user's identity. Only a user in possession of a private key that corresponds to the public key at the server will be able to authenticate successfully. The private keys need to be stored and handled carefully, and no copies of the private key should be distributed. The private keys used for user authentication are called identity keys.

To update the SSH keys the following fields has to be provided,

• Key Pair - Public and Private - In the SSH public key authentication use case, it is rather typical that the users create (i.e. provision) the key pair for themselves. SSH implementations include easily usable utilities for this (for more information see ssh-keygen)
• Public key File Upload - The Public Key File will be of .pub extension .
• Private Key File Upload - Private Key File can be of any extension
• Upload Keys - On clicking Upload Keys the content public key can be seen in below table.