Kerberos registration not available on the agent but enabled on the server

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
Answer
bsok
Messages: 2
Registration: June 15, 2022 - 4:01 PM

December 4, 2025 - 4:33 PM

Hello,

Since version 2.6.1.17576 on Wapt Discovery, the agent no longer allows the use of Kerberos registration, even if it is enabled on the server side.
After installing the agent on a new machine, the wapt-get.ini file contains the following instruction:
use_kerberos=0.
When trying to generate a Wapt agent from the console, the "Use Kerberos for initial agent registration" option is grayed out.
By editing the file and setting use_kerberos=true, and then restarting the Wapt service, the machine can register with the server via Kerberos.
Is it possible to configure waptagent.exe to automatically set use_kerberos=true during installation instead of use_kerberos=0?

Is this a limitation of Wapt Discovery?
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

December 5, 2025 - 9:44 AM

bsok wrote: Dec 4, 2025 - 4:33 PM Is this a limitation on Wapt Discovery?

We do have a commit to that effect on our end, dated December 22, 2023:

[FIX] kerberos option is not available in Discovery

It's just the GUI that's causing the problem (I'm looping internally to see if we change our minds).
Answer