Common "Invalid Signature" status

There are a few threads talking about “Invalid Signature” status from a submitted action. There is so little explanation to really help to explain what it means and how actually fix it.

The doc says:

Invalid Signature: The Action cannot run due to an invalid signature.

Of course the action failed due to that error. It does not really explain what signature is looking for and how to determine what is invalid Where to look for invalid signature and is it the actionsite.afxm file gets corrupted.

It would be really nice to provide some tips to diagnose the issue and how to fix it.

The way to fix is to uninstall the BESClient and reinstall it again. It seems to help but then this problem comes back again a few days later. So we really need to determine what is causing this error so that it does not re-happen again after reinstalling the besclient.

Any suggestions… Thanks.

1 Like

That will probably require a PMR so the support team can check your deployment with you. The only times I’ve seen this involved someone hand-editing the Bigfix database, and one case where old actions were still active from an operator who had been deleted.

2 Likes