Invalid signature after upgrade waptserver

[chnateag]

Good morning,


We just updated our WAPT server. I kept my private/public keys and certificate in the POST configuration. We regenerated a new agent, but when I try to deploy it, I keep getting invalid signature errors

Code: Select all

id;description;summary;start_date;logs
59;Installation of pc33.local.exemple.net (=13) (task #59);Exception: Package file c:\wapt\cache\pc33.local.exemple.net.wapt signature is invalid;2017-06-23T17:08:29.685000;"Exception: Package file c:\wapt\cache\pc33.local.exemple.net.wapt signature is invalid
Traceback (most recent call last):
  File ""c:\wapt\waptservice\waptservice.py"", line 2100, in run
    self.running_task.run()
  File ""c:\wapt\waptservice\waptservice.py"", line 1360, in pwrapper
    return func(*arg, **kwargs)
  File ""c:\wapt\waptservice\waptservice.py"", line 1420, in run
    self._run()
  File ""c:\wapt\waptservice\waptservice.py"", line 1822, in _run
    self.result = self.wapt.install(self.packagename,force = self.force)
  File ""c:\wapt\common.py"", line 4108, in install
    raise Exception(u'Package file %s signature is invalid' % ensure_unicode(fname))
Exception: Package file c:\wapt\cache\pc33.local.exemple.net.wapt signature is invalid
"

The only information I can find on the mailing lists is that my package isn't signed with the same certificates, but that's definitely the case, so I checked the dates and regenerated the agent several times! Furthermore, it does appear in the repository with the new version.
I also cleared the server and machine caches while I was at it, and restarted the services, but no improvement

I double-checked the ssl directory in c:/wapt and it's the correct one

Thanks in advance for any help and ideas; I'm completely out of them

[agauvrit]

The certificate you use when creating the agent must match the private key normally used for signing packages (i.e., the waptupgrade package).

Is this correct?

Which version of WAPT are you using?

Sincerely,

Alexandre

[chnateag]

The CRT file for me is the very first one that was generated during our initial installation, along with the P12 and PEM files. Yes, they correspond.
We've now upgraded to the latest version, 1.3.12.15.