In the DataPower WebGUI, select Administrator->Crypto Tools and then Generate Key after entering the following values. See the related URLs section below for more information on Crypto Tools.

In the "Common Name (CN)" field, enter the user name to be authenticated in the SSH server.

Do not set a password, leave the password field blank.

Export Private Key = on which exports the private key to the temporary folder on the appliance so that it can be recovered if necessary.

In the SSH Client Profile object configuration

Enter the "User Name" to be used to authenticate in the SSH server (the same user name you used in the key's Common Name)

Check the Public Key checkbox, and uncheck the Password check box to ensure only public key authentication will be used.

Choose the new key you created in the User Private Key pull down menu.

Leave the other settings with default values.

Export the RSA public key data

The DataPower setup is complete. You will now configure the SSH server to allow for public key authentication of the DataPower client using the user name you configured.

Although configuration requirements will depend on your SSH server, you may need to append the public key data from the RSA key to an authorized keys file on the SSH server. One easy way to extract the RSA public key data is to use a new DataPower crypto tool newly available in 3.8.1.x firmware:

Go to "Administration->Crypto Tools" in the DataPower WebGUI.

On the main panel, click on "Convert Crypto Key Object" tab.

Select the private key you want to use on the pull down menu

Enter a file name, for example temporary:///publickeyexport.pub.

Click on "Convert Crypto Key Object".

Download the file created.

Use the exported RSA public key data to configure your SSH server Refer to the documentation for your SSH server for information on how to include the RSA public key data you have exported in the SSH server configuration. In some cases, you might add the one line from the file into an authorized_keys file on the SSH server. Follow instructions on the the location and permissions required for the configuration files you update.