Tranquil IT Forum

Kevin-LH76 wrote: ↑Feb 16, 2026 - 10:26 So the agent needs to be installed on the machine that runs the script?

Yes

Kevin-LH76 wrote: ↑Feb 16, 2026 - 10:26 In all cases, is the password hardcoded into a file?

You can modify the script to read the password from a separate file. This way, it's not hardcoded into the script

Kevin-LH76 wrote: ↑Feb 16, 2026 - 10:26 Can we launch it directly on our WAPT server which is on RedHat?

No, this meant that the WAPT server has a private key that signs packets, and so it very strongly discouraged from a safety point of view

And also for another problem, see:
viewtopic.php?p=16830#p16830

Thank you for your feedback.

Isn't it more secure to use encryption functions like the example below:

https://www.wapt.fr/en/doc-1.8/wapt-cre ... aquet.html

The deployment doesn't happen on every machine, so it's not necessary.

This script runs regularly on a management machine, not on all machines.

Good morning,

We created the Python script, but with some adjustments

• The path, login, and password are passed as parameters rather than hardcoded in the script

• Sensitive data is encrypted using a certificate

• The account used for the script is dedicated to this task

• A PowerShell script retrieves the sensitive data and launches the Python script

Currently being tested, this function addresses our problem.

The matter can perhaps be closed, thank you for your help

Hi Kevin,

thanks for the feedback. I'm marking the topic as resolved.

Denis