In the Hashicorp vault connector, we have a mechanism to cache the JWT token to avoid generating the token call for every request. The validity of the cache token is one percent less than the actual value set for the token expriy on the vault end.

There is a limitation in Vault end, where a token generated by one replica can't be used on another replica. Due to this, if, in any condition, the delegate has a cache token for replica B and makes a call to replica A, it fails.

We need a mechanism from the Harness end to invalidate the cache on the delegates for this vault.