Hi Denis,
I saw this morning that a new version (2.7.0.19633) has been released. I haven't seen a changelog yet, but I've noticed that Mac authentication (without using a manually generated Kerberos token) is still broken:
Screenshot 2026-10-22 121415.png
I had to...
The search returned 35 results
- October 22, 2026 - 12:47
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Self-service problem following WAPT 2.7 update
- Answers: 5
- Views : 7443
- October 13, 2026 - 09:07
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Self-service problem following WAPT 2.7 update
- Answers: 5
- Views : 7443
Re: Self-service problem following WAPT 2.7 update
Hi Denis,
The problem in our case with the Macs is that our domain isn't accessible to the machines when they log in, only via a VPN that only runs once the session is open.
As a result, password rotation doesn't work, among other things.
We had to deploy MDM on these...
The problem in our case with the Macs is that our domain isn't accessible to the machines when they log in, only via a VPN that only runs once the session is open.
As a result, password rotation doesn't work, among other things.
We had to deploy MDM on these...
- October 8, 2026 - 4:43 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Self-service problem following WAPT 2.7 update
- Answers: 5
- Views : 7443
Re: Self-service problem following WAPT 2.7 update
I've made some progress; you need to use the Kerberos name in uppercase: yoann.montouchet@AD.XXX.FR in the kinit command, and use a temporary file to store the token, then export the path to the token: `
kinit -c FILE:/tmp/krb5cc_$(id -u) yoann.montouchet@AD.XXX.FR
export KRB5CCNAME ...`
kinit -c FILE:/tmp/krb5cc_$(id -u) yoann.montouchet@AD.XXX.FR
export KRB5CCNAME ...`
- October 8, 2026 - 3:12 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Self-service problem following WAPT 2.7 update
- Answers: 5
- Views : 7443
Self-service problem following the WAPT 2.7 update
Hello,
We upgraded to version 2.7.19598 yesterday on our server (enterprise license). The server is running Debian 13 Trixie (also upgraded yesterday; previously we were on Debian 11 and then Debian 12).
Since this upgrade, we've noticed a change in behavior regarding self-service...
We upgraded to version 2.7.19598 yesterday on our server (enterprise license). The server is running Debian 13 Trixie (also upgraded yesterday; previously we were on Debian 11 and then Debian 12).
Since this upgrade, we've noticed a change in behavior regarding self-service...
- March 2, 2026 - 5:24 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Wapt self-service on macOS
- Answers: 10
- Views : 15671
Re: wapt self-service on macos
Okay, the first command fails on the problematic Mac:
>>> client = pyldap.PyLdapClient(domain_name="ad.xxx.xx")
>>> print(client.bind_sasl_kerberos())
(False, '')
It works on the Windows machine; my AD account appears correctly.
The second command works:
>>> pyldap.cldap_get ...
>>> client = pyldap.PyLdapClient(domain_name="ad.xxx.xx")
>>> print(client.bind_sasl_kerberos())
(False, '')
It works on the Windows machine; my AD account appears correctly.
The second command works:
>>> pyldap.cldap_get ...
- March 2, 2026 - 4:26 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Wapt self-service on macOS
- Answers: 10
- Views : 15671
Re: wapt self-service on macos
I just pulled up another Mac that appears correctly in the OU, but we're getting the same message as the Mac that's giving us trouble today. Could it be related to our infrastructure? We're on a Samba-AD server at the AD level, but it's only accessible through a VPN.
EDIT: I tried the same command on a...
EDIT: I tried the same command on a...
- March 2, 2026 - 2:57 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Wapt self-service on macOS
- Answers: 10
- Views : 15671
Re: wapt self-service on macos
That's strange, it seems it can't connect to Active Directory even though it's reachable, and I was able to add an Active Directory user on my end:
Screenshot 2026-03-02 145457 (Small).png
I'm going to try rebooting and starting again
. EDIT: It's the same after rebooting, VPN connected and...
Screenshot 2026-03-02 145457 (Small).png
I'm going to try rebooting and starting again
. EDIT: It's the same after rebooting, VPN connected and...
- March 2, 2026 - 1:31 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Wapt self-service on macOS
- Answers: 10
- Views : 15671
Re: wapt self-service on macos
Yes, it still works. I can confirm that the self-service package was the missing element. I don't know why adding it earlier didn't make everything work, but it's fine now.
Removing the package leaves the self-service area empty, and...
Removing the package leaves the self-service area empty, and...
- March 2, 2026 - 1:22 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Wapt self-service on macOS
- Answers: 10
- Views : 15671
Re: wapt self-service on macos
I confirm that the server configuration appears to be OK:
----------------------------------------------------------------
Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Username: yoann.montouchet
Group test member ...
----------------------------------------------------------------
Test SSO SELFSERVICE LDAP with ldap_account_service_login
----------------------------------------------------------------
Username: yoann.montouchet
Group test member ...
- March 2, 2026 - 1:08 PM
- Forum: WAPT usage (Console, Agent) / WAPT usage (Console, Agent)
- Subject: Wapt self-service on macOS
- Answers: 10
- Views : 15671
Wapt self-service on macOS
Hello everyone,
I'm sorry to bother you with what seems like such a trivial problem, but I'm tearing my hair out trying to configure a WAPT agent on macOS 26.3.
The machine is freshly installed, the connection to the domain is OK, and the VPN is set up.
The machine is visible in the WAPT console, but...
I'm sorry to bother you with what seems like such a trivial problem, but I'm tearing my hair out trying to configure a WAPT agent on macOS 26.3.
The machine is freshly installed, the connection to the domain is OK, and the VPN is set up.
The machine is visible in the WAPT console, but...
