Attention

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

The post-configuration script rewrites the nginx configuration. A backup file is created when running the postconf in the same directory.

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 >

  • Choose a password (if not defined) for the SuperAdmin account of the WAPT Server (minimum length is 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 to be registered.

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

    • Choice #3 does not activate the kerberos authentication mechanism for theinitial registering of hosts equipped with WAPT. The WAPT Server will require a login and a password for each host registering with it.

WaptAgent Authentication type?

--------------------------------------------------------------------------
(x) 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 >

  • If you want to use WAPT for OS Deployment, select yes.

Do you want to activate os deployment?

        < Yes >        < No >

  • If you said yes to activate os deployment, postconf will ask you if you want to use a secure authentication in order to deploy your os. It will ask a user/password when you’ll try to deploy os.

Would you like to activate secure authentication on wads ?

        < Yes >        < No >

  • Still about wads, if you said yes to the 2 last questions, you’ll have a final question :

Would you like to mention subnet ip exempt from wads authentication

        < Yes >        < No >

If you said yes here too, you’ll have to give subnet ip, can be a list for example : 192.168.0.0/24,192.168.1.0/24

  • 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 >

  • Fill in the FQDN of the WAPT Server.

FQDN for the WAPT Server (eg. wapt.example.com)

---------------------------------------------
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 WAPT Server.

                                  < OK >

Listing of post-configuration script options:

Options

Description

--force-https

Configures Nginx so that port 80 is permanently redirected to 443