The Secure Node agent is available for Windows, Linux, and Mac operating systems. This article will show you how to install the Linux RPM package version of the client.
Secure Nodes can be used to access resources that are based in external networks that you are not able to route to by other means. The Secure Node agent maintains a tunnel between networks so that you can publish resources on your Hypersocket server as if they were local LAN services.
The Secure Node feature should be installed on the server (in the top navbar from Updates, Features & Licensing->Features->Secure Node).
Click on the download link for the feature and accept the license agreement that appears. Restart the Hypersocket server when prompted.
Before the agent can be installed and configured, you must have a Secure Node resource created and configured on the server (see Getting Started Guide or Administrator's Manual)
Step 1 – Download the agent
The Secure Node agent is required to be able to route to resources in other networks. Installing the agent requires sudo or root access. All commands below assumed you are logged in as root.
To get the agent installer the user should first log on to the Hypersocket web interface, then click on the Downloads button in the top navbar. In the Downloads page that appears, click on the link for the correct client operating system. We will demonstrate the Linux client here.
Step 2 – Installing the client
Before you install the client, you need to download the private key from the key pair that was generated during the configuration of the Secure Node resource that should already have been created.
Log on to the web UI as admin and navigate to Service Keys. For the key you want, click the green Gears icon next to the key and click Download Public Key.
Save the resulting .pub flie that will be downloaded.
There are two methods to install, command line and GUI. To install via the command line go to the location the file was placed and enter the following:
rpm -i secure-node-linux-VERSION.deb
Allow the process to complete and the client will now be available.
It may be possible to install via the Desktop GUI, but on the test install of Fedora used in this guide, the default OS tools did not allow installation of the rpm this way.
Step 3 - Configuring the agent
Move the public key file that was downloaded into /opt/secure-node/conf/default/ and rename it to server.pub.
mv /pathtofile/securenodename.pub /opt/secure-node/conf/default/server.pub
Create a new file (with sudo or root) in /opt/secure-node/conf/default called agent.properties containing the following:
agent.name=Secure Node 1
Replace the name, host and port as required for your configuration and save the file.
Step 4 - The Secure Node service
The agent install creates a service called secure-node which should automatically start on reboot.
Now there is a valid configuration, we can start the service manually with:
sudo service secure-node start
If the service has started successfully, the agent should create a directory called /opt/secure-node/conf/default/hostkeys. If it does not do this, just stop and restart the service again as sometimes it needs two starts to operate initially.
You may now continue to configure the Server Agent Routes on the server and then publish your resources.