Kerberos registration not available on the agent but enabled on the server
Published: Dec 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?
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?