Tranquil IT Forum

WAPTConsole Enterprise version 2.2.1.11957
Console: Win19 server
SRV: Debian 11

Hello,

I would like to update WAPT from version 2.2 to version 2.4.

I was wondering about the authentication mechanism in the post-configuration script. During the initial installation, I chose not to use any authentication method.

If I change this during the update to, for example, use option 3), will I risk affecting the workstations already present in the console?

If it won't have any impact, could you also explain how the two available authentication methods work: Kerberos and option 3)?

Thank you in advance,

Eliott.

Hello Eliott,

the authentication method in question refers to the initial registration of workstations. Once a workstation is registered, a CSR (Customer Sign-On) is required to sign its client certificate, which is then used to authenticate to the WAPT server.

For Kerberos operation/configuration, you can refer to the online documentation; it's quite comprehensive.

Note: For login/password authentication, if you need to perform silent registration to avoid having an admin account lingering in .bat files or elsewhere, you can create a basic local user on the WAPT server just for registration, restricting its permissions with ACLs (Access Control Lists). However, the best option is still to register via Kerberos, but if you have no other choice, there is this alternative.

Best regards,

Denis