
Chapter 3: Operations | 25 |
|
|
Server Security command, SSH password authentication will use either the access rights from the local user database or the values returned by the RADIUS server.
With either of the “or” methods (PWKEY and KEYPW), the user access rights are determined from the method used to authenticate the user.
With either of the “and” methods (PW&KEY and KEY&PW), the user access rights are determined from the first method specified. If PW&KEY is specified, the access rights from the password authentication will be used. If KEY&PW is specified, the access rights from the key authentication will be used.
For more information, see Using Authentication Modes in this chapter.
SSH user keys
A user’s SSH key is specified in a User Add or User Set command. You may define a key even if SSH is not currently enabled. The key may be specified in one of two ways:
•When using the SSHKEY and FTPIP keyword pair to define the network location of a user’s SSH key file, the SSHKEY parameter specifies the name of the uuencoded (UNIX to UNIX encoded) public key file on an FTP server. The maximum file size that can be received is 4K bytes. The FTPIP parameter specifies the FTP server’s IP address.
When this method is specified, the CCM initiates an FTP client request to the specified IP address. The CCM then prompts the user for an FTP user- name and password for connection. When connected, the CCM will GET the specified key file and the FTP connection will be closed. The CCM then stores the SSH key with the username in the CCM user database.
•When using the KEY keyword to specify the SSH key, the KEY param- eter specifies the actual uuencoded SSH key. This is for configurations that do not implement an FTP server. The CCM stores the specified key in the CCM user database.
The CCM processes a uuencoded SSH2 public key file with the format described in the IETF document
You may also generate SSH user keys via AVWorks. See the AVWorks Installer/ User Guide.