Installing Wapt 1.5 under Centos

[hasop]

Hello,

I installed Wapt for the first time on CentOS.
I believe I followed the installation documentation for this system to the letter.
Everything went smoothly until the Windows console installation step (https://www.wapt.fr/wapt-1.5/Configuration/index.html).

Indeed, there is no .exe file in the specified path.
During my tests with a Windows server, I remember generating the files directly from the Windows console. What about with a Linux server? Did I miss a step in the documentation?

Thank you in advance for your help.

[sfonteneau]

There is a small error in the document:

missing:

Code: Select all

yum install tis-waptsetup

[hasop]

That definitely changes everything!
Thank you

[hasop]

I managed to install the console with its various certificates (it wasn't the easiest thing).

During the wapt-setup installation, I got the message in a console:
"Please get login for add_host:"

I must have responded incorrectly, because it moved on to something else, but my PC isn't visible.

So I launched the register from the command line using my admin username and password, but it doesn't seem to be what's expected:
C:\Windows\system32>wapt-get register
Please get login for add_host:admin
Password:
FATAL ERROR: HTTPError: 401 Client Error: Unauthorized for url: https://xxxx/add_host

Any ideas?

[sfonteneau]

Do you want to configure workstation authentication?

Kerberos or strong authentication.

when you launch:

Code: Select all

python /opt/wapt/waptserver/scripts/postconf.py

One step offers you Waptagent authentication type.

To activate "without authentication", this is the first option
To activate Kerberos, it's the second option
To enable ID/password authentication, it's the 3rd option

Depending on the choice, the agent will ask:

- 1 nothing
- 2. Nothing if the workstation is in the domain and the WAPT server is correctly configured for Kerberos
- 3. The username and password for the wapt console

[hasop]

Option 2, but I only have two choices:
- Allow unauthenticated registration
- Require strong authentication...

Does this mean the Kerberos installation is faulty?
How can I check?

[sfonteneau]

Option 2, but I only have 2 choices:
- Allow unauthenticated registration
- Require strong authentication...

Does this mean the Kerberos installation isn't working correctly?
How can I check?

Indeed, Kerberos authentication does not seem to be working correctly.

Is the position in the right field?

[hasop]

Normally, yes.
I just noticed that after restarting the post-installation, the "use_kerberos" parameter reverted to False.
Setting it back to True doesn't change anything, however.

Since this is an experiment, I'm going to try disabling Kerberos everywhere and switching to a basic mode.

(EDIT after some experimentation) => Registration works correctly with the following server options in waptserver.ini:
use_kerberos = False
allow_unauthenticated_registration = True

[benoitpatin]

Hello,

I have the same problem.
I restarted my server configuration and selected option 2, then rebooted.
I reinstalled the client on a machine that is in the domain, but I still get the "add_host" prompt.