[RESOLVED] Waptupgrade and verify_cert packages

[l.costes]

Hello,
I've enabled SSL verification (certificate signed by an internal CA).
Certificate verification works fine for newly deployed agents or when forcing the configuration on client machines.

To automate the configuration of existing clients, I created a new WaptUpgrade package, checking the "Verify SSL" box and pointing to a concatenated certificate + CA file.

However, upgrading the WaptUpgrade package (via self-service or the console) doesn't change this configuration on already installed machines.
I still have the parameter `[global] verify_cert=0`.
Any ideas?


- Installed WAPT version: 1.8.1
- Server OS: RHEL 7.7
- Administration/package creation machine OS: Windows 10

[sfonteneau]

Yes, that's a problem today...
If the version is identical, you can right-click on the waptupgrade package and click on "Force Installation".

[sfonteneau]

Otherwise, in the file:

C:\Program Files (x86)\wapt\waptupgrade\setup.py

You can add:

Code: Select all

def install():
    force=True

Then restart the generation of an agent

[dcardon]

Hello l.coste,

you can also modify the wapt-get.ini files with a WAPT package, see https://wapt.tranquil.it/store/tis-wapt-conf-policy.

As Simon indicated, currently the waptupgrade package only upgrades the client if the agent's executable version has changed; it ignores the package version suffix (similar to install_exe_if_needed). We're looking into whether to change this behavior in a future version.

Regards,

Denis

[l.costes]

Thanks for your replies!

I preferred to create a dedicated configuration package as suggested; I haven't yet developed the habit of creating separate packages,
but this product is amazing, the possibilities are enormous,

congratulations on your work!!

Also, just to understand the first question:
what does the file C:\Program Files (x86)\wapt\waptupgrade\setup.py manage?

We'll get the license in 2021; it's in the budget.