Secure Node agent installation on Linux (DEB)

system

Introduction

The Secure Node agent is available for Windows, Linux, and Mac operating systems. This article will show you how to install the Linux DEB 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 LogonBox server as if they were local LAN services.

 

Prerequisites

The Secure Node feature should be installed on the server (in the top navbar from Updates, Features & Licensing->Features->Secure Node).

Note: This feature is already installed on our LogonBox public cloud servers.

 

Click on the download link for the feature and accept the license agreement that appears. Restart the LogonBox server when prompted.

 

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.

To get the agent installer the user should first log on to the LogonBox 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 DEB client here.

 

Step 2 – Installing the client

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 then proceed to step 3:

sudo dpkg -i secure-node-linux-VERSION.deb

To install through the desktop GUI instead, enable executable permissions for the file and double click the deb file to run the installer. We're using Linux Mint here so the Package Installer launches and displays the Secure Node Client. Click Install Package to start the install.

 

When prompted, enter the sudo password and click OK. Allow the client to install and click Close when completed.

 

Once the installation has completed you can close the Package Installer.

  

Step 3 - Connecting to your server

The secure node makes an outbound connection to LogonBox server in the cloud, the agent requires authentication details to connect to your tenant to configure it for use with your on-premise directory. The configuration will guide you through a series of steps.

You now need to run the autoconfigure program to complete your install.

From a terminal, do:

sudo sh /opt/secure-node/autoconfig

 

You will need to provide the following:

  • Server hostname - this is the name of your cloud tenant, typically, <client name>.logonbox.com
  • Username - the name of the administrator or someone with permissions to administer the tenant
  • Password - the associated password for the user (note the password is not echoed to the screen as you type, but type the password and press enter and it will accept it).

If successfull, the configuration will be connected to your tenant.

Now that a connection is established, the configuration requires a name for this node in addition to access policies.

 

You will be asked to set a name for this node, which defaults to the local hostname.

When you are asked if you would like to access any other hosts from this node, choose Y.

Enter the hostname of your AD server (or other server type if not using AD), or the fully qualified domain name.

You may enter multiple hostnames if required, press enter on a blank line to complete.

 

You will now be asked if you want to set up a connection to your AD service now. If you choose No here, you can set this up later in the UI, otherwise you can create a simple connection from this prompt now on your LogonBox server.

The autoconfig part is now complete.

 

Step 4 - The Secure Node service

The agent install creates a service called secure-node which should automatically start on reboot and should have started already.

If you need to start the service manually, you can run the following:

sudo service secure-node start

 

Check on the server in Networking->Secure Nodes and you should see your configuration showing as Online.