Attention : support for WAPT 1.8.2 ended on June the 30th 2022.

There are known vulnerabilities in WAPT dependencies in WAPT 1.8.2 branch. Please upgrade to the latest supported version. CVE listing (non exhaustive) :
  • * python engine : python 2.7 (CVE-2020-10735, CVE-2015-20107, CVE-2022-0391, CVE-2021-23336, CVE-2021-3177, CVE-2020-27619, CVE-2020-26116, CVE-2019-20907, CVE-2020-8492, etc.)
  • * cryptography : openssl : CVE-2022-2068, CVE-2022-1292, CVE-2022-0778, CVE-2021-4160, CVE-2021-3712, CVE-2021-23841, CVE-2021-23840, CVE-2021-23839, CVE-2020-1971, CVE-2020-1968, CVE-2019-1551
  • * python dependencies : cryptography (CVE-2020-36242, CVE-2020-25659), eventlet (CVE-2021-21419), jinja2 (CVE-2020-28493), psutil (CVE-2019-18874), waitress (CVE-2022-31015), lxml (CVE-2021-4381, CVE-2021-28957, CVE-2020-27783, CVE-2018-19787), ujson (CVE-2022-31117, CVE-2022-31116, CVE-2021-45958), python-ldap (CVE-2021-46823)

Upgrading WAPT from 1.3 to 1.6 on CentOS/ RedHat

Note

We make the assumption that your WAPT Server is installed on a basic minimal install of CentOS7 (x64). If this is not the case, you may follow the documentation to upgrade your base server.

This procedure aims to explain the migration of WAPT 1.3 to 1.6, only.

The main differences between these two versions of WAPT are:

Element

WAPT 1.3

WAPT 1.6

Database

MongoDB

PostgreSQL

Web server

Apache2

Nginx

WAPT agent

agent listening on agent port 8088

agent initiating and maintaining a websocket with the server.

Signature

sha1 hashes

a Code Signing certificate is required, control file attributes are signed with sha256 hashes.

These changes require to follow scrupulously several operations for a smooth upgrade.

Uninstalling WAPT 1.3 from the CentOS/ RedHat server

yum remove tis-waptrepo tis-waptsetup tis-waptserver
systemctl stop httpd
systemctl disable httpd

Configuring the CentOS/ RedHat server

localectl set-locale LANG=en_US.utf8
localectl status
yum update
yum install epel-release wget sudo unzip
wget https://wapt.tranquil.it/tools/mongo-tools_centos7_2.6.zip -O /tmp/mongo.zip
unzip -j mongo.zip -d /bin/

Updating the CentOS / RedHat server

cat > /etc/yum.repos.d/wapt.repo <<
[wapt]
name=WAPT Server Repo
baseurl=https://wapt.tranquil.it/centos7/wapt-1.6/
enabled=1
gpgcheck=0
EOL

yum install postgresql96-server postgresql96-contrib

Installing WAPT 1.6 on the CentOS / RedHat server

yum install tis-waptserver
sudo /usr/pgsql-9.6/bin/postgresql96-setup initdb
sudo systemctl enable postgresql-9.6 waptserver nginx
sudo systemctl start postgresql-9.6 nginx

Note

The installation may ask you for the Kerberos realm. You may ignore it by pressing Enter to go on to the next step.

Launching the post-configuration script

Note

  • we advise that you launch the post-configuration steps after each server upgrade so that the server uses the latest configuration format;

  • it is not required to reset a password for the WAPT console during the post-configuration step;

/opt/wapt/waptserver/scripts/postconf.sh

The post-configuration step will offer you to change the password or to move to the next step, you may choose to change the password if desired.

The post-configuration step will then detect that the current version is 1.3 and it will try to launch the process of migrating the MongoDB database to PostgreSQL. Validate this step.

The post-configuration step will next offer you to configure the Nginx web server. Validate this step.

Starting up WAPT on the CentOS/ RedHat server

systemctl enable waptserver
systemctl start waptserver

Cleaning up the CentOS/ RedHat server

At the end of the migration process, it is necessary to clean the WAPT Server.

WAPT will use from now on Nginx as its web server and PostgreSQL as its database server.

yum remove httpd mongodb

Installing the new WAPT console

  • download waptsetup: https://srvwapt.mydomain.lan/wapt/waptsetup-tis.exe;

  • start the installation; the configuration of the WAPT repository and server URLs has not changed;

  • open the waptconsole by selecting C:\Program Files (x86)\wapt\waptconsole.exe (default location) or C:\wapt\waptconsole.exe (older WAPT versions);

  • check that the WAPT Server works correctly by clicking on the wrench icons and the button Verify!

You may now go to the next step to generate the necessary keys.