Documentation

Server Management

Installing the Windows Credentials Provider
User Accounts
Roles
Authorized Keys
Event Logs
Email Messages
HTML templates
Session Management
Authentication Modules
Authentication Policies
SMTP Configuration

User Interface

Branding
User Interface Themes

Getting started with Nodal VPN

Introduction

This article is intended to guide you through the 7 steps required (and 1 optional) to deploy a new Nodal VPN configuration by providing links to the relevant article for each step.

1. Signing up for Nodal VPN

Jadaptive’s Nodal VPN is a hybrid cloud/on-premises solution.

All your configuration and authentication is managed by a cloud-hosted tenant, but the VPN clients will connect directly to your locally install Nodal Agent.

The first step is to to register your new cloud tenant.

Signing up for Nodal VPN

---

2. Deploying the Nodal Agent

Once your tenant is available, you will then need to install the on-prem part of the solution, this is called the Nodal Agent.

A Nodal Agent is the endpoint that your VPN clients will be connecting to and comes as a pre-built VM image. You can find documents for the most popular hypervisors here:

Deploying Nodal Agent on Proxmox

Deploying Nodal Agent on VMware ESXi

Deploying Nodal Agent on Hyper-V

---

3. Creating a VPN Network

Once you have a Nodal Agent connected to your tenant, you now need to define a VPN Network.

A VPN network defines the IP range for your clients and which Nodal Agent they should connect through.

Creating a VPN Network

Creating a VPN Network

---

4. Setting up your users

At this stage, you can now configure the users of your system.

Here you have a choice, you can either create some local users directly in your VPN tenant, or you can connect to your on-premise Active Directory using The Windows Connect service. It is also possible to have a combination of both as you can still create local users once you are connected to AD.

Creating User Accounts

Installing Windows Connect

---

5. Client Configuration settings

Now we can set up a Client Configuration.

A Client Configuration defines which IP ranges your VPN clients can route to and which users can use this configuration.

Nodal VPN Client Configuration

---

6. Configure Authentication (optional)

The final step of configuration in your tenant could be to review your Authentication Policies. The default authentication will be to use just username and password, but if you wanted to add in any 2FA, an Authentication Policy is where this is done.

There are several Authentication Policies. a Default Authentication Policy for web UI logins, a Password Reset Policy, but most importantly for the VPN, there is the VPN Client Policy, which handles authentication via the VPN Client.

It is also possible to add multiple policies so you can define differing authentications for different groups of user.

To learn more about Authentication Policies, refer to the following article:

Configuring Authentication Policies for User Login

To learn more about the authentication methods that can be used:

Configuring Authentication Modules

---

7. Installing the Nodal VPN client

You can now start to install the Nodal VPN clients. Installers are available for Windows, MacOS and Linux systems:

Installing the Windows VPN client

---

8. Connecting a Nodal VPN Client

With the VPN client installed, all that needs to be done is to tell the client to connect to your new VPN system:

Connecting the Nodal VPN Client