Topic - Public key authentication with many users, multiple client platforms, or multiple user ids

Many users

The following are some considerations for public key authentication if you have many users accessing either the same user id or different user ids:

• As described earlier, if you leave the value for a parameter blank in the Public Key Authentication group of the SSH configuration window, then when the end user starts the session Host On-Demand uses the default value for the parameter. Click here for more information about these default values.

• Each workstation that launches an SSH client requires a keystore file. However, keystore files on different workstations can have the same file name (and therefore share the same session profile) even if the contents of each keystore are different.

Multiple client platforms

The following are some considerations for public key authentication if you have users accessing the same user id or different user ids from different client platforms.

• Consider leaving the File Path for KeyStore parameter blank. When the end user starts the session, if the File Path for KeyStore was left blank, Host On-Demand uses the default path and file name. Click here for more information about default values.

Multiple user ids

The following are some considerations for public key authentication if you have one or more users that need to access more than one user id on the same SSH server, or user ids on more than one SSH server.

• One keystore file can contain multiple private keys, or one keystore file with a single private key can be used for all the user ids, or multiple keystore files can be used, one for each user id.