Mapping an SSH Key or Private Key Passphrase for Authentication

You are viewing documentation for a version of Secret Server that is no longer supported. Delinea supports Secret Server for one year after release. This version has passed that window and will no longer receive updates. We strongly recommend upgrading to a supported version. Visit the current version of this page for the latest documentation.
For release dates, end-of-support timelines, and upgrade guidance, see the Secret Server Product Lifecycle page.
You can view the latest version of the Secret Server documentation here.

Some password changers may be customized to use SSH key authentication. Secret Server needs to know which text-entry fields contain the key and the passphrase. These text-entry fields can be specified after clicking Edit from the password changer page.

1558036208687

The key and passphrase must be identified by a $ sign and the secret text-entry field name, which can be obtained from the secret template.

To set which text-entry fields are your key and passphrase, go to the extended mappings for a secret template by clicking Extended Mappings from the Secret Template Edit page. Select the text-entry fields that correspond to the SSH private key and passphrase if applicable. No matter what you name your key text-entry field, Secret Server knows what it is. This is set up by default, so you should not need to do this unless you've created custom Unix templates you want to use keys with.

Once Secret Server knows which text-entry fields contain the private key and private key passphrases, it can automatically use them as a part of launchers.