Page 1 of 1

[RESOLVED] Active Directory authentication problem on the WAPT console.

Published: March 8, 2022 - 3:01 PM
by Admin-CAB
Hello everyone,

I've consulted the forum on this topic but haven't been able to solve my problem...

I can't authenticate to the WAPT console using an Active Directory account.

I've correctly modified the settings in the Opt/wapt/conf/waptserver.ini file as recommended. The path seems correct. But despite this, I still can't use an AD account to log in to the console.

I've checked with telnet on port 389 of my DC server, and the connection is working.

Do you have any idea what the problem might be? Here is a copy/paste of my waptserver.ini file


wapt_admin_group_dn= CN=adm-postes,OU=IT,DC=xxx,DC=xxx,DC=fr
ldap_auth_server= srv-adds01.xxx.xxx.fr
ldap_auth_base_dn= DC=xxx,DC=xxx,DC=fr
ldap_auth_ssl_enabled=False
secret_key = xxxxxxxxxxxxxxxxxxxxxxxx
server_uuid = xxxxxxxxxxxxxxxxxxxxxxxx
wapt_huey_db = /opt/wapt/db/waptservertasks.sqlite
wapt_password = xxxxxxxxxxxxxxxxxxxxxxxxxxx
waptwua_folder = /var/www/html/waptwua
allow_unauthenticated_registration = True
allow_unauthenticated_connect = True
clients_signing_key = /opt/wapt/conf/ca-srv-wapt.xxxxxxx.fr.pem
clients_signing_certificate = /opt/wapt/conf/ca-srv-wapt.xxxxxxxx.fr.crt

Thank you for your feedback.

Re: Active Directory authentication problem on the WAPT console.

Published: March 8, 2022 - 8:20 PM
by sfonteneau
Hello,

is the account you're logging in with part of the "protected users" group in Active Directory?

Note: you can now use
`wapt_admin_group = adm-postes`
instead of `wapt_admin_group_dn`.

Simon Fonteneau