Installing WAPT Server on Ubuntu

Setting up the GNU/Linux Ubuntu server

In order to install a fresh Ubuntu Linux server 20.04 LTS Focal Fossa (physical or virtual) please refer to the Ubuntu GNU/Linux Installation Guide.

Warning

  • install 64bits version;

  • install without graphical interface;

  • only LTS version are supported by WAPT;

Danger

Nginx is the ONLY supported web server for WAPT. Apache is no longer supported in WAPT.

Configuring network parameters

The different parameters presented below are not specific to WAPT; you may adapt them as required for your environment.

Modify the following files in order to get a proper naming (FQDN) and network addressing strategy.

In the following example:

  • the FQDN name is srvwapt.mydomain.lan;

  • the short-name of the WAPT Server is srvwapt;

  • the DNS suffix is mydomain.lan;

  • the IP address is 10.0.0.10/24;

Configuring the name of the WAPT Server

Hint

The short name of the WAPT Server must not be longer than 15 characters (the limit is due to sAMAccountName restriction in Active Directory).

The name of the WAPT Server must be a FQDN, that is to say it has both the server name and the DNS suffix.

  • modify the /etc/hostname file and write the FQDN of the server;

# /etc/hostname of the WAPT server
srvwapt.mydomain.lan
  • configure the /etc/hosts file, be sure to put both the FQDN and the short name of the server;

# /etc/hosts of the WAPT server
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.0.0.10   srvwapt.mydomain.lan     srvwapt

Hint

  • on the line defining the DNS server IP address, be sure to have the IP of the server (not 127.0.0.1), then the FQDN, then the short name;

  • do not change the line with localhost;

Configuring the IP address of the WAPT server

  • configure the IP address of the WAPT Server in the /etc/network/interfaces;

# /etc/network/interfaces of the WAPT server
auto eth0
iface eth0 inet static
  address 10.0.0.10
  netmask 255.255.255.0
  gateway 10.0.0.254
  • apply the network configuration by rebooting the machine with a reboot;

  • if it has not already been done, create the DNS entry for the WAPT Server in the Organization’s Active Directory or in your DNS server;

  • after reboot, configure the system language in English in order to have non-localized logs for easier searching of common errors;

apt install locales-all
localectl set-locale LANG=en_US.UTF-8
localectl status
  • check that the machine clock is on time (with NTP installed);

dpkg -l | grep ntp
service ntp status
date

Hint

If the NTP package is not installed.

apt install ntp
systemctl enable ntp
systemctl start ntp
  • update and upgrade your Ubuntu;

    apt update && apt upgrade -y
    
  • install systemd;

    apt install systemd
    
  • install certificates;

    apt install ca-certificates
    
  • restart server;

    reboot
    

The Ubuntu server is now ready. You may now go on to the next step and install WAPT on your Ubuntu.

Attention

The upgrade procedure is different from installation. For upgrade, please refer to the documentation on upgrading the WAPT Server.

Installing the WAPT Server requires a few steps:

  • configuring the repositories;

  • installing additional Linux packages;

  • installing and provisioning the PostgreSQL database;

  • post-configuring the WAPT Server;

Note

The WAPT Server packages and repository are signed by Tranquil IT and it is necessary to get the gpg public key below in order to avoid warning messages during installation.

Configuring DEB repository

The configuration of repositories for WAPT Enterprise and WAPT Discovery Edition differs. Make sure to choose the right one!

During installation, you may be asked for the kerberos realm. Just press Enter to skip this step.

Discovery

Important

Follow this procedure for getting the right packages for the WAPT Discovery Edition. For WAPT Enterprise Edition please refer to the next block.

Note

Not Available as of 2021-06-04.

WAPT Discovery will be release later. For the free version, refer to wapt-1.8 documentation https://www.wapt.fr/en/doc-1.8/.

Enterprise

Important

Follow this procedure for getting the right packages for the WAPT Enterprise Edition. For WAPT Discovery Edition please refer to the previous block.

To access WAPT Enterprise resources, you must use the username and password provided by our sales department.

Replace user and password in the deb parameter to access WAPT Enterprise repository.

apt update && apt upgrade -y
apt install apt-transport-https lsb-release gnupg
wget -O - https://wapt.tranquil.it/debian/tiswapt-pub.gpg  | apt-key add -
echo "deb https://user:password@srvwapt-pro.tranquil.it/entreprise/ubuntu/wapt-2.0/ $(lsb_release -c -s) main" > /etc/apt/sources.list.d/wapt.list

Important

Follow this procedure for getting the right packages for the WAPT Discovery Edition. For WAPT Enterprise Edition please refer to the previous block.

Installing the WAPT Server packages

apt update
apt install tis-waptserver tis-waptsetup

Post-configuring

Attention

For post-configuration to work properly, you must first have properly configured the hostname of the WAPT server. To check hostname configuration use the command echo $(hostname) which must return the hostname that will be used by WAPT agents on client computers.

Hint

This post-configuration script must be run as root.

  • run the script:

    /opt/wapt/waptserver/scripts/postconf.sh
    
  • click on Yes to run the postconf script:

    do you want to launch post configuration tool?
    
           < yes >          < no >
    
  • enter the password for the SuperAdmin account of the WAPT Server (minimum 10 characters);

    Please enter the wapt server password (min. 10 characters)
    
    *****************
    
    < OK >          < Cancel >
    
  • confirm the password;

    Please enter the server password again:
    
    *****************
    
    < OK >          < Cancel >
    
  • choose the authentication mode for the initial registering of the WAPT agents;

    • choice #1 allows to register computers without authentication. The WAPT server registers all computers that ask;

    • choice #2 activates the initial registration based on kerberos. (you can activate it later);

    • choice #3 does not activate the kerberos authentication mechanism for the initial registering of machines equipped with WAPT. The WAPT server will require a login and password for each machine registering with it;

      WaptAgent Authentication type?
      
      --------------------------------------------------------------------------
      (*) 1 Allow unauthenticated registration
      ( ) 2 Enable kerberos authentication required for machines registration.
          Registration will ask for password if kerberos not available
      ( ) 3 Disable kerberos but registration require strong authentication
      --------------------------------------------------------------------------
                          < OK >          < Cancel >
      
  • select OK to start WAPT Server;

    Press OK to start waptserver
    
           < OK >
    
  • select Yes to configure Nginx;

    Do you want to configure nginx?
    
       < Yes >        < No >
    
  • enter the FQDN of the WAPT Server;

    FQDN for the WAPT server (eg. wapt.mydomain.lan)
    
    ---------------------------------------------
    wapt.mydomain.lan
    ---------------------------------------------
    
          < OK >          < Cancel >
    
  • select OK and a self-signed certificate will be generated, this step may take a long time …

    Generating DH parameters, 2048 bit long safe prime, generator 2
    This is going to take a long time
    .......................................+...............................+...
    

Nginx is now configured, select OK to restart Nginx:

The Nginx config is done.
We need to restart Nginx?

       < OK >

The post-configuration is now finished.

Postconfiguration completed.
Please connect to https://wapt.mydomain.lan/ to access the server.

                 < OK >

Listing of post-configuration script options:

Flag

Description

--force-https

Configures Nginx so that port 80 is permanently redirected to 443.

The server is now ready. You may go to the documentation on installing the WAPT console.