[RESOLVED] Self-Service Malfunction

Share your tips or issues concerning the WAPT Console or WAPT Agent here
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

January 14, 2025 - 10:14

Code: Select all

/opt/wapt/waptserver/scripts/testing-ldap-connectivity.sh
----------------------------------------------------------------
Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Username : mullert
Group test member : Domain Users
----------------------------------------------------------------
[OK] Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Test ldap with direct Login
----------------------------------------------------------------
Username ldap: mullert
Password ldap:
Group test member : Domain Users
--------
ALL GOOD
--------
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

January 14, 2025 - 10:15

However, with another group of which I am a member:

Code: Select all

/opt/wapt/waptserver/scripts/testing-ldap-connectivity.sh
----------------------------------------------------------------
Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Username : mullert
Group test member : caduser
----------------------------------------------------------------
[FAIL] username mullert not in group caduser
----------------------------------------------------------------
{'success': True, 'groups': [], 'error': False, 'msg': ''}
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 14, 2025 - 10:22

I'm unsure about the uppercase/lowercase settings;

are the groups entirely lowercase everywhere?

Is there a specific DN base in the WAPT configuration?
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

January 14, 2025 - 10:26

@tomtom: Just wondering if you're experiencing the same issue as me: if you change the authentication method in the self-service configuration package to "system", does the self-service feature appear? (You'll need to enter a login/password)
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

January 14, 2025 - 10:27

Here is my waptserver.ini:

Code: Select all

[options]
wapt_user = adminwapt
wapt_password = password
wapt_folder = /var/www/wapt
server_uuid = 67837244-907c-11e6-86b1-005056add68a
secret_key = secret
use_kerberos = True
allow_unauthenticated_registration = False
waptwua_folder = /var/www/waptwua
allow_unauthenticated_connect = False
signature_clockskew = 72000
clients_signing_key = /opt/wapt/conf/ca-waptserver.fr.hydac.int.pem
clients_signing_certificate = /opt/wapt/conf/ca-waptserver.fr.hydac.int.crt
remote_repo_support = True
wapt_admin_group = FR-WAPTADMINS
ldap_auth_ssl_enabled = False
ldap_account_service_login = FR-SVC-LDAP@fr.hydac.int
ldap_account_service_password = password
wapt_huey_db = /opt/wapt/db/waptservertasks.sqlite
loglevel_waptserver = info
loglevel_waptcore = info
glpi_server_endpoint = https://fr-for-glpi/glpi/plugins/fusioninventory/index.php
glpi_server_user = fr-svc-glpi
glpi_server_pass = password
glpi_inventory_update_delay = 4
glpi_inventory_update_range = 20
glpi_server_pause_timeout = 20,15
wads_enable = True
token_secret_key = secret
clients_signing_crl = /var/www/ssl/ca-waptserver.fr.hydac.int.crl
clients_signing_crl_url = http://waptserver.fr.hydac.int/wapt/ssl/ca-waptserver.fr.hydac.int.crl
ssl_additional_crls = /var/www/ssl
ad_domain_name = fr.hydac.int
The groups are exactly as written in the "Domain Users" script, with uppercase letters and "caduser" in lowercase
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

January 14, 2025 - 10:29

clafon wrote: Jan 14, 2025 - 10:26 AM @tomtom: just to know if you're in the same situation as me: if you change the authentication method in the self-service configuration package to "system", does the self-service appear? (you'll need to enter a login/password)
I tested it and indeed, with service_auth_type=waptserver-ldap -> not working (empty Self Service) and service_auth_type=system -> OK after entering credentials

However, no selectable categories...
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 14, 2025 - 11:31

TomTom wrote: January 14, 2025 - 10:15 However, with another group of which I am a member:

Code: Select all

/opt/wapt/waptserver/scripts/testing-ldap-connectivity.sh
----------------------------------------------------------------
Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Username : mullert
Group test member : caduser
----------------------------------------------------------------
[FAIL] username mullert not in group caduser
----------------------------------------------------------------
{'success': True, 'groups': [], 'error': False, 'msg': ''}
This specific case, as shown in testing-ldap-connectivity.sh, interests me
Can you contact our support team so I can see it live?
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 14, 2025 - 11:55

The problem has been reproduced internally.

It's clearly a capitalization issue.

I've put a 'tis' group into testing

within the 'Tis' self-service rule package,

in the 'ad tiS' group

. A temporary solution would be to convert all groups to lowercase.

We'll therefore perform the comparisons ignoring case sensitivity.
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

January 14, 2025 - 5:17 PM

So it's strange because the test fails with the group "caduser" which is in lowercase, though.
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 14, 2025 - 5:56 PM

TomTom wrote: Jan 14, 2025 - 5:17 PM So it's strange because the test fails with the group "caduser" which is in lowercase though.
Yes, in that case there is still a problem for you.

Can you contact us by phone to look into this, mentioning that it was Simon who asked us to call?
Locked