Setting Up a User's Public Key on the Server

Public key authentication is an alternative to password authentication, providing a more secure authentication method that allows users to avoid entering or storing a password, or sending it over the network. A user generates a key pair (a public key and a private key) on the client computer and provides the public key to the administrator of the remote computer running Connect Server. The administrator sets up the client user's public key as described in the steps below.

For information on how to create public keys, see Creating SSH Keys.

Important: The Web UI currently does not support key-based authentication. This feature is for transfers initiated in the application (including the Hot Folders) or the ascp command.
  1. Obtain the client user's public key.

    The client user should send you a secure email with the public key pasted in the message body or attached as a text file.

  2. Install the public key in the user account on the server.

    In the home directory of the account that clients will use to access the server, create a directory called .ssh (if it doesn't already exist). In that folder, save the key file and name it authorized_keys. If authorized_keys already exists, append the key file to it.

    In the example that follows:

    • aspera_user_1 is the server user account.
    • /tmp/id_rsa.pub is where you have saved the public key.
    • /home/aspera_user_1/.ssh/authorized_keys is where to install the public key

    Run the following commands to install the client's public key:

    # mkdir /home/aspera_user_1/.ssh
    # cat /tmp/id_rsa.pub > /home/aspera_user_1/.ssh/authorized_keys

    Run the following commands to change the key directory and keyfile's ownership to user aspera_user_1, to allow access by the aspera_user_1 group, and to set permission bits:

    
    # chown -R aspera_user_1:aspera_user_1  /home/aspera_user_1/.ssh
    # chmod 700 /home/aspera_user_1
    # chmod 700 /home/aspera_user_1/.ssh
    # chmod 600 /home/aspera_user_1/.ssh/authorized_keys