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.
[RESOLVED] Post-conference script info request
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
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
