[SOLVED] Error message: checkPackageSignature failed

[corriou]

Good morning,

I use package groups to create profiles for my different types of workstations. I rarely modify these groups, but I wanted to add a package to one of them today.
When I clicked the button Build Uploada window Error in application opened with the following message:

Error when uploading package: CheckPackageSignature failed for Administration(=83). Sign waptKey:.

I carried out other tests:
- modifying other groups => still the same error
- Creating a new group => OK, then modifying this new group => error message similar to the previous one
- Updating a package from the tranquil.it repositories => OK

Unfortunately, I cannot say from which version of Wapt the problem appeared.
My server (version 2.3.0.13516) is installed on Debian 11. My console (under Windows) uses the same version.

Sincerely,

[blemoigne]

Hello,
Is your public certificate (.crt) used to sign packages/actions located in c:\program files (x86)\wapt\ssl?
Best regards,
Bertrand

[llecaplain]

I have the same problem and the certificate is definitely present

[dcardon]

@llecaplain Wapt version, Wapt edition, server OS, client OS, etc. See forum rules + use cases (upgrade, fresh install, etc.).

Thank you, best regards,

Denis

[corriou]

My certificate was located in a C:\private directory, but the path was correct in the settings.
I moved it to c:\program files (x86)\wapt\ssl and then changed the personal certificate path in the local WAPT configuration. When I check the associated key, it matches the certificate, but I still encounter the same error.

To clarify:
- WAPT Discovery (but the window displays WAPTConsole Enterprise version) is version 2.3.0.13516, obtained by upgrading from the previous version (I generally keep up with all versions).
- Debian 11 OS for the server
- Windows 10 22H2 for the console

[sfonteneau]

In the private repository section of wapt,

can you sort by the "signatory" column to identify if you have multiple keys? Is it the same signer for all keys?

Then, when you search for your management machine in the inventory on your management machine, does the same certificate appear in the "Certificate" tab? Are

the files in your C:\Program Files (x86)\wapt\ssl directory .crt files?

Did you restart the console after adding the certificates to C:\Program Files (x86)\wapt\ssl?

[corriou]

Indeed, I have two different signers appearing, one for a single package, the most recent one. The older packages are signed with a different key.
So, I remembered that during the last update, I deleted the old configurations (using "Clean up old configurations" in waptsetup.exe), and when rebuilding them, I must have gotten confused. I might also have forgotten to check the " Install certificates provided by this installer". Probably a day when I was very tired.

Anyway, reinstalling the console via waptsetup (with the correct settings) solved my problem.

PS: I did have .crt files in my directory, and the console had also been restarted.

PS2: For the package with the wrong certificate, I simply reverted to a (not so) old version and modified it again to use the correct certificate.

Thank you for your help, always so quick and efficient.

[dcardon]

Hi Alain,

thanks for your feedback.

We'll try to add a clearer message during installation to avoid confusion.

Denis