Getting Invalid Signature from Telesign

[dylanreich]

Hi, I have been using this successfully for a while now, but for some reason my SMS request are no longer working. Here is what I'm getting back from Telesign:

{\"status\":{\"code\":10008,\"description\":\"Invalid Signature.\",\"updated_on\":\"2019-11-01T00:26:16Z\"}}

I'm not sure if this means the provider is no longer pulling my credentials, or something to do with how the provider is adding the authentication to the headers.

Once in a blue moon the request succeeds for some reason and I get the text.

[Andrewangeta]

Hmmmmm im not sure. If the provider has been successfully sending sms then I don't know how the signature could be correct one time and incorrect another time. Are you sure you haven't reset your API keys by accident maybe?

[dylanreich]

I haven't reset my API keys, and I went in and verified everything should be good with my Telesign account. I have my app deployed to a Kubernetes cluster; I'm not how the signature generation is done or if being behind a load balancer would cause any issues. I would say that that was the main change that occurred (I wasn't on a cluster before), however my usage of the feature was very low before, so it's tough say for sure if that caused it to stop working; I can for sure say that it has worked a few random times while deployed on the cluster.