Google Cloud Secrets Engine "SignatureDoesNotMatch"

Vault
1

Have you seen errors that resemble this?

<?xml version='1.0' encoding='UTF-8'?>
<Error>
    <Code>SignatureDoesNotMatch</Code>
    <Message>Access denied.</Message>
    <Details>The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.</Details>
    <StringToSign>GET\n\n\n1737853801\n/path/to/file.json</StringToSign>
</Error>

I am using Vault with Nomad. I have applications that get GCP (Google Cloud Platform) credential through a Vault GCP secrets engine. When the secrets get renewed, Nomad will trigger the applications to restart so that they can use the new credentials provided to them via Vault. However, it has been happening very often over the last year that sometimes the credentials are not valid for a while (eventual consistency?) and so we get the errors as listed above.

I am wondering if anyone else has seen a similar scenario.