(Optional) Create a file called identification in your %USERPROFILE%\Application Data\SSH\UserKeys directory.

Edit it with your favorite text editor to include the following line (replace mykey with the name you gave to the key pair in the Key Generation wizard):

IdKey     mykey

With SSH Tectia Client 5.x, using the identification file is not necessary if all your keys are stored in the default directory and you allow all of them to be used for public-key and/or certificate authentication. If the identification file does not exist, the Connection Broker attempts to use each key found in the %USERPROFILE%\Application Data\SSH\UserKeys directory.

You can also add other directory locations on the Keys and Certificates page of the SSH Tectia Configuration tool. See Managing Keys and Certificates.

Connect to Server using some other authentication method and copy your public key (for example, mykey.pub) to your authorized_keys directory ($HOME/.ssh2/authorized_keys on Unix servers, %USERPROFILE%\.ssh2\authorized_keys on Windows servers).

Note

SSH Tectia Server 4.x (or older) requires an authorization file stored in the .ssh2 directory. The authorization file specifies the public keys that are authorized for login. The authorization file may be optionally used with SSH Tectia Server 5.x as well. An example file %USERPROFILE%\.ssh2\authorization is shown below: Key authorized_keys\mykey.pub This directs SSH Tectia Server to use mykey.pub as a valid public key when authorizing your login.