Tranquil IT Forum

WAPT version installed: 2.3
- Server OS (Linux Ubuntu)
- Administration/package creation machine OS (Windows Server 2022)

Hello,
I am currently testing WAPT (Enterprise). I am in the certificate creation phase (first console launch).
I am a little lost on the personal certificate creation phase:
- Is this a certificate for package generation?
- Is it linked to the account that ran the console?
- Can we use a certificate generated by our internal organization?

Thank you in advance.

Mikael wrote: ↑March 28, 2023 - 4:08 PM I am currently testing WAPT (Enterprise). I am at the certificate creation phase (first launch of the console).
I am a little lost on the personal certificate creation phase:
- is it a certificate for generating packages?

Yes, that's the certificate used to sign packets when the packet is created, or when sending notifications to client machines (the messages are also signed)

- Is it linked to the account that ran the console?

The certificate is somewhat independent of console authentication. While the certificate can be shared by multiple users, it is recommended to create one for each system administrator for traceability purposes.

- Can we use a certificate generated by our internal organization?

It's possible to use the organization's internal PKI. However, you must be careful to generate code-signing certificates for signing software packages. Therefore, I recommend starting by using certificates generated through the WAPT console.

To be exhaustive, we can point out that there is also a pki integrated into WAPT for the authentication part of WAPT agents, but there is no need to worry about it unless you want to activate certificate-based authentication directly on nginx (to be done later once you have mastered the tool).

Sincerely,

Denis

Hello,
sorry I didn't see your message, thank you for your reply.
Indeed, I proceeded that way for my tests; I will look into an internal Code Signing certificate later.

Okay, thanks for the feedback, Mikael
Denis