Tranquil IT Forum

Wapt Community: 1.8.2 (Linux)
Infrastructure: Windows 10

Hello
, When I try to create a new account to use the console (creating a new user certificate), I end up with a user who can only view the interface; they cannot change the configuration of the workstations, for example.

On the same installation, if I use my certificate, it works without any problem, so it's not a problem with the Wapt client configuration on the workstation.

What am I missing?

Sincerely,
Tom

Hello,
This is the expected behavior...

To modify the machine's configuration, you must copy the certificate of this new user to the c:\program files(x86)^wapt\ssl directory of the machines that must be manageable by this user (and restart waptservice on these machines for the certificate to take effect).

The other option (with the Enterprise version) is to deploy an "authority" certificate (CA) on the machines and sign the certificates of the various users with the private key of this CA. The client workstations will then accept packets and actions signed by all users from this CA.

Ah OK, I hadn't noticed that detail!

Thank you, it works perfectly.

So, what method should be used to propagate the new certificates?