Hello,

for those who might have the same problem, it will be fixed in future versions of Wapt.

Thank you all for your help!

Here it is:

[options]
waptwua_folder = /var/www/waptwua
server_uuid = a480287a-a79c-11e8-ac90-fe149ee36605
wapt_password = XXXXXXXXXXXXXXXXXXx
allow_unauthenticated_registration = True
secret_key = XXXXXXXXXXXXXXXX
use_kerberos = True
allow_unauthenticated_connect = True
wapt_admin_group_dn = CN ...

Do you have any idea what could be causing this blockage?

I just tested the debugging, and I got this result:

2018-12-20 11:06:41,414 DEBUG Traceback (most recent call last):
File "/opt/wapt/waptserver/server.py", line 927, in login
raise EWaptAuthenticationFailure('Authentication failed.')
EWaptAuthenticationFailure: Authentication failed.

Is there a system that allows testing the WAPT/AD connection with logs?

Hello,

However, when I use my AD login credentials to try to open the console with my domain account, authentication fails.

My account is indeed in the Waptadmins AD group, which is in the correct OU (as indicated in the ini file).

I don't understand...

Hello,

As mentioned, the console is returning some Active Directory information (but authentication is failing).

For the command: telnet srv00.xxxx.local 389

, here is the result:


Trying 192.168.1.200...
Connected to srv00.xxxx.local.
Escape character is '^]'.

Connection closed by foreign ...

So, my WAPT server is able to communicate with Active Directory, but I don't understand why I can't authenticate with an AD account on the console, even though:

My group is located at: xxxx.local/Groups/waptadmins
In the attributes: CN=waptadmins,OU=Groups,DC=xxxx,DC=local
My accounts...

Hello,

I just did a quick check and it seems the AD connection is working, since on the left side of WAPT, I can see the OUs that contain workstations and therefore add packages to the workstations in these OUs (this information may be coming through the information feed...).

However, after the telnet command, I have the impression that the connection to LDAP is working, but the connection to the AD account remains impossible