Tranquil IT Forum

WAPT version: 1.7.4
Server OS: CentOS 7
Console OS: Windows 10

Hello,
I'm still developing a software program, but I've encountered a problem. The software aims to allow a user managing a room (a room containing computers) to choose which software is installed in their room. The software is largely finished but has a problem: the installation doesn't start automatically after adding the package to the computer. By looking at the code, I was able to find out how the server and client communicate (socket) and that installation from the API no longer works since version 1.5. I would therefore like to know if there is a way to launch this installation from a Python module, or if I need to modify the socket so that it interprets the request, or if plugin support is planned.

Thank you.

Hi Joey,

since WAPT version 1.5, actions on workstations are handled through WebSocket connections initiated by the user's workstation. Furthermore, these actions are now also signed, like installation packages. The best way to understand how the actions are performed is to delve into the console's Python code. The issue isn't that the API no longer works, but rather that security has been tightened.

Regards,
Denis

Hello, thank you for the quick reply. So, if I understand correctly, it should be possible to create an external component that launches the installation on the workstations, provided I use the certificate in my request

Hello Calvibald,

Calvibald wrote: ↑Feb 14, 2020 - 9:09 AM Hello, thank you for the quick reply. So, if I understand correctly, it should be possible to create an external component that launches the installation on the workstations, provided that I use the certificate in my request.

There's nothing preventing this from working. However, from an architectural standpoint, it's important to clarify that in your scenario, the web server will become a highly sensitive asset because it will have to host the signing key.

In the WAPT security model, the signing key remains on the administrator's workstation and is never available on the server. This ensures the integrity of the workstations even if the server were to be compromised.

Sincerely,

Denis

Great, thank you! I'll specify this private key issue in the software documentation since it's quite important