I am currently testing the Discovery version of WAPT.
Everything went well, I installed the server with Kerberos authentication and created an agent which I installed on a client machine.
The client is correctly appearing in the console, that's perfect.
I imported a simple package (tis-opera in this case) that I wanted to deploy on my client machine.
And there, it's impossible; the automatic installation initiated by the server never happens.
Installed versions:
- Server: Debian 12 + WAPT 2.4.0.14143
- Console agent: Windows 11 Pro + Setup 2.4.0.14143
- Client Agent: Windows 11 Pro + Agent 2.4.0.14143
Some clues that might help in solving the problem:
- On the client machine, when I run `wapt-get install tis-opera`, the package installs correctly. And I can see the installed package from the console.
- On the client machine, when I launch the self-service interface and log in with my AD user account (the one on my client machine), I can see that the package is offered, but it's not installed.
If I click "Install," it installs perfectly.
- I don't appear to have any problems with Kerberos or my certificates:
Code: Select all
2023-11-06T16:07:24.902100+01:00 wapt waptserver[348058]: 2023-11-06 16:07:24,902 [waptserver ] DEBUG About to check supplied data signature with certificate info-p-ale2.lpl.intra 2023-11-06T16:07:24.902401+01:00 wapt waptserver[348058]: 2023-11-06 16:07:24,902 [waptserver ] INFO Data successfully checked with certificate CN info-p-ale2.lpl.intra for info-p-ale2.lpl.intra
- The hardware and software inventories are being updated perfectly. I can see in the server logs that the database is correctly updated when the client starts (SQL update query).
- In the console, when I click on "Launch installations", I can see tasks arriving on the client:
- Updated list of available packages
- Installing updates
- Clear the package cache
It therefore appears that the system is up to date even though a package is not installed.Get package index from [ https://xxx.domain.fr/wapt>, https://xxx.domain.fr/wapt-host for host_id info-p-ale2.lpl.intra>]
3 package(s) in repository.
The system is up to date.
- When I go to https://xxx.domain.fr/api/v3/login_kerberosAfter entering my AD client username/password, I get: A little surprised by the edition which is supposedly in "Enterprise" mode when I'm on Discovery.
I'm starting to wonder if this isn't a limitation of the Discovery version, but the comparison with the Enterprise version doesn't reveal any differences at this level.
If anyone has any ideas, I'm all ears
Thanks in advance !
