Public key exchange from “Enterprise Cloud Server” to “Terminal Server”

[Steve92]

Hello,

I meet a quite difficult use case during the POC.
On an “Enterprise Cloud Server”(ECS),  when I add a “Terminal Server”(TS) as a node to this ECS, if I well understand, I’m asked to enter credentials of an administrator of TS to allow the public key of ECS to be copied to TS.

I don’t know and don’t have to know these credentials.

So, I have to send i.e. by email the public key of ECS to the admin of TS.

When must she/he put this public key on TS side ?

Thanks,

Regards,

Steve.

[Britgirl]

In general, when adding a node to the cloud server, you don’t have to copy any key, the procedure to add the node will propagate the key for the node to use. To do that, you need the admin credentials on the node, the Terminal Server host in your case.

However, when you don’t have admin permissions on the node you want to add, for example there are two separate administrators for both machines, you can indeed pass the CS public key to the admin of the TS Node, and they can place it in the appropriate directory. On Linux, the public key can be found in the directory, for example in /usr/NX/etc/keys/node.localhost.id_rsa.pub. You, the CS admin, can then proceed to add the node to the Cloud Server with sudo /etc/NX/nxserver –nodeadd IP_of_node –node-name name_of_node.

See the article here:  https://www.nomachine.com/AR11V01258.

 

[Steve92]

I’ve tested to add the public NX key of Cloud Server to Terminal Server to /var/NX/nx/.nx/config/autorized.crt (from memory).

“config” directory has to be created (with right permissions) if it’s the 1st node to be added. (Cat node..rsa.key.pub >>  /var/NX/nx/.nx/config/autorized.crt)

Please, could you confirm it’s OK ?

It seems to be OK but I want to be sure not to forget something.

Thanks !

Regards.

Steve

 

 

[Author]

Posts