Page 2 of 4
Re: Self Service Malfunction
Published: Dec 18, 2024 - 08:18
by TomTom
Hello Simon,
No, it's launched with a standard user account. Do I need to re-run it as root?
Okay, I launched it as root. It's asking me for a username and then a group it's supposed to belong to, is that right?
If I enter the information in this way, here is the output:
Code: Select all
/opt/wapt/waptserver/scripts/testing-ldap-connectivity.sh
----------------------------------------------------------------
Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
DEBUG:root:Dn username not found
Username : mullert
Group test member : caduser
DEBUG:root:(|(&(distinguishedName=CN=Muller\, Thomas,OU=Users,OU=Forbach,OU=Agences-HYDAC,DC=fr,DC=hydac,DC=int)(primaryGroupID=1637))(&(member:1.2.840.113556.1.4.1941:=CN=Muller\, Thomas,OU=Users,OU=Forbach,OU=Agences-HYDAC,DC=fr,DC=hydac,DC=int)(sAMAccountName=caduser)))
----------------------------------------------------------------
[FAIL] username mullert not in group caduser
----------------------------------------------------------------
{'success': True, 'groups': [], 'error': False, 'msg': ''}
Re: Self Service Malfunction
Published: January 13, 2025 - 3:34 PM
by TomTom
Hello,
could someone please look into this?
I'm still unable to get my Self working via LDAP authentication.
Thanks in advance,
Thomas
Re: Self Service Malfunction
Published: January 14, 2025 - 09:08
by Clafon
We are encountering the same problem, yet the waptserver.ini file seems to be correctly configured
Code: Select all
[options]
secret_key = 2D23c3Rba7wgEkd10qM7Jps8sFYxlQToxM0ybytbxhlHEb9eEJlqTbYFRcpsHMGO
token_secret_key = XsdBd6Hy9mebQ9V2CwnwE2igvscb7ELutlZQyHE11PxLgcLXPOl6UV1LTWEM9bR6
server_uuid = 5c849d8f-5f14-47cd-9622-e4479a471f04
waptwua_folder = /var/www/waptwua
wapt_huey_db = /opt/wapt/db/waptservertasks.sqlite
wapt_password = $pbkdf2-sha256$29000$UGrtPWdM6f1/r7U25twbQw$PAFU3GThtk6ulnXq09ruqGxjGWCd2Re9O0oTZrdg2SI
allow_unauthenticated_registration = False
clients_signing_key = /opt/wapt/conf/ca-SRV-WAPT.domain.local.pem
clients_signing_certificate = /opt/wapt/conf/ca-SRV-WAPT.domain.local.crt
clients_signing_crl = /var/www/ssl/ca-SRV-WAPT.domain.local.crl
clients_signing_crl_url = http://SRV-WAPT.domain.local/wapt/ssl/ca-SRV-WAPT.domain.local.crl
ssl_additional_crls = /var/www/ssl
use_kerberos = True
ldap_account_service_login = compte_de_service
ldap_account_service_password = mdp_compte
ldap_auth_base_dn = dc=domain,dc=local
ad_domain_name = domain.local
ldap_nesting_group_support = True
ldap_primary_group_ad_support = True
wapt_admin_group = GL_RIT
login_on_wads = False
The connection test /opt/wapt/waptserver/scripts/testing-ldap-connectivity.sh seems to be OK:
Code: Select all
----------------------------------------------------------------
Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Username : clafon
Group test member : GL_RIT
----------------------------------------------------------------
[OK] Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Test ldap with direct Login
Re: Self Service Malfunction
Published: January 14, 2025 - 09:35
by sfonteneau
Hello,
for TomTom, you should upgrade to the latest version to see if it's better; you seem to be using the previous version. We've made some changes.
For Clafon, your connectivity script seems to be working correctly. So the connection to the console is working?
Is it just the self-service that isn't working? Are you using the same configuration as TomTom?
In wapt-get.ini: service_auth_type=waptserver-ldap? Or is it something else?
Re: Self Service Malfunction
Published: January 14, 2025 - 09:41
by Clafon
on a user's workstation
Code: Select all
[global]
use_hostpackages=1
use_kerberos=1
use_ad_groups=False
allow_remote_reboot=1
allow_remote_shutdown=1
max_gpo_script_wait=180
pre_shutdown_timeout=180
hiberboot_enabled=0
repo_url=https://srv-wapt.domain.local/wapt
wapt_server=https://srv-wapt.domain.local
verify_cert=C:\Program Files (x86)\wapt\ssl\server\SRV-WAPT.domain.local.crt
include_dmi_inventory=1
include_wmi_inventory=1
peercache_enable=0
service_auth_type=waptserver-ldap
allow_cancel_upgrade=False
waptaudit_task_period=1h
[default_global]
use_hostpackages=1
use_kerberos=1
use_ad_groups=1
allow_remote_reboot=1
allow_remote_shutdown=1
max_gpo_script_wait=180
pre_shutdown_timeout=180
hiberboot_enabled=0
repo_url=https://srv-wapt.domain.local/wapt
wapt_server=https://srv-wapt.domain.local
verify_cert=C:\Program Files (x86)\wapt\ssl\server\SRV-WAPT.domain.local.crt
include_dmi_inventory=1
include_wmi_inventory=1
peercache_enable=0
[waptwua]
enabled=True
include_potentially_superseded_updates=False
download_scheduling=1d
install_at_shutdown=True
install_delay=7d
[default_waptwua]
enabled=True
include_potentially_superseded_updates=True
download_scheduling=1d
install_at_shutdown=True
install_delay=7d
sfonteneau wrote: ↑Jan 14, 2025 - 9:35 AM
For clafon, your connectivity script seems to be working correctly. So the connection to the console is working?
I didn't understand the question, sorry
Re: Self Service Malfunction
Published: January 14, 2025 - 09:53
by sfonteneau
In your configuration, I see that you have a wapt_admin_group.
Does your problem therefore only concern self-service, or also the connection to the console with login and password?
Re: Self Service Malfunction
Published: January 14, 2025 - 09:54
by Clafon
For your information, when you change the self-configuration package to "system" instead of "waptserver-ldap", the packages appear in the store after you enter your login/password.
When you switch back to "waptserver-ldap", the store empties.
Re: Self Service Malfunction
Published: January 14, 2025 - 09:54
by Clafon
sfonteneau wrote: ↑Jan 14, 2025 - 09:53
In your configuration, I see that you have a wapt_admin_group.
So your problem only concerns self-service, or also the connection to the console with login and password?
The administration console works very well
Re: Self Service Malfunction
Published: January 14, 2025 - 10:06 AM
by TomTom
sfonteneau wrote: ↑Jan 14, 2025 - 9:35 AM
Hello,
For TomTom, you should upgrade to the latest version to see if it's better; you seem to be on the previous version. We've made some changes.
For Clafon, your connectivity script seems to be working correctly. So the connection to the console is working?
Is it just the self-service that isn't working? Are you using the same configuration as TomTom?
In wapt-get.ini: service_auth_type=waptserver-ldap? Or is it something else?
Hello Simon,
I'm on the latest version, I just forgot to change my signature, sorry.
Thomas
Re: Self Service Malfunction
Published: January 14, 2025 - 10:07 AM
by sfonteneau
TomTom wrote: ↑January 14, 2025 - 10:06
sfonteneau wrote: ↑Jan 14, 2025 - 9:35 AM
Hello,
For TomTom, you should upgrade to the latest version to see if it's better; you seem to be on the previous version. We've made some changes.
For Clafon, your connectivity script seems to be working correctly. So the connection to the console is working?
Is it just the self-service that isn't working? Are you using the same configuration as TomTom?
In wapt-get.ini: service_auth_type=waptserver-ldap? Or is it something else?
Hello Simon,
I'm on the latest version, I just forgot to change my signature, sorry.
Thomas
The fact that you have the line DEBUG:root:(|(&(distinguishedName=C in the script indicated an older version, that's why.
Can you test the script again?