To configure an ssh connection to a remote Compute Server using a public key and a private key requires:
An EASA Server will work as any other ssh client.
For testing, we recommend installing a third party ssh client like putty. We will also use putty to generate the keys for the Windows example.
EASA uses Java for ssh file operations, which uses an sftp implementation; Thus sftp must be enabled.
To enable sftp for openssh on linux,
It does not matter where the private key and public key are created, the private key will be installed on the client machine (the EASA Server) and the public key will be used for any ssh server, in this case, the remote Compute Server
We can do this just using the following command:
If this command was run on the remote Compute Server then the public key can stay in that machine, the private key has to be moved to the client machine (EASA Server ). In that case SAMBA will be needed to make a share between the UNIX machine and Windows machine, or you can use any other approach to move the file. Be careful with the permissions of the private key file, as it is 600, so maybe you will need to change the permissions to 755 or something like that to be able to take the file remotely.
Also copy the public key file to any other remote Compute Servers that require this kind of ssh authentication.
An ssh server has to be running on this machine, we will need to create a folder under the user which will be used to connect through SSH. In my case, I have an user called user1 on this machine and its path to its home folder is /home/user1:
Now we use putty to connect from the client machine to the remote machine.
The private key file must be installed in the file system of the client machine:
Otherwise if it does not work it will say something like:
Now everything is ready to configure EASA to use the private key to connect with the remote Compute Server. The private key has to be somewhere in the file system of the EASA Server.