There are two scenarios where you might want a customer to use their own ssh keys to login to a server:
For this situation you can simply add the customer’s public key to the root user’s ssh authorized_keys file. This file is usually located in the ~/.ssh folder. Just open it up with your favorite editor (NANO is easiest) and paste in the customer’s public SSH key.
nano ~/.ssh/authorized_keys
Notice that in this case the customer does not have to reveal their private key to you.
For this situation you have to swap out your keys in the WPCD records for the customer keys. But first, you need to make sure that the customer’s PUBLIC key is added to the root user’s ssh authorized_keys file (see option 1 above).
Then, you need to update the server records to override the default global keys defined in SETTINGS :
To test the keys, you can use the SSH CONSOLE tab to run the ls command. If you get a popup with a list of files you’ll know all is good.
For this situation the customer will need to reveal their private key to you or you will need to generate a keypair for them.
For more information about the KEYS tab see our documentation for SSH KEY OVERRIDES.