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)

Configuring WAPT

The WAPT Server having been successfully installed, the next steps are as follow:

• Installing the WAPT management console
• Generating the Administrator’s certificate for signing WAPT packages
• Configuring the WAPT console
• Building the WAPT agent installer
• Deploying the WAPT agent for Windows
• Deploying the WAPT Agent on Linux
• Deploying the WAPT agent on MacOS
• Deploying the Linux WAPT Agent with Ansible

To go further, more configuration options are available in this part of the documentation:

• Configuring the WAPT agent
• Configuring the WAPT console
• Configuring the WAPT Server
• Configuring WAPT Server for large deployments

To uninstall WAPT agent properly

• Uninstalling WAPT agent from clients