We are facing an issue with api keys. This is happening randomly. Sometimes, when calling the api, we get error: “key is not authorized”. So we regenerate another key for the api.
Do you think that existing keys get expired upon a specific change in the api? I’m not sure why this happens.
Lastly, if you are using Hybrid out of the box, the redis that comes installed with that container is just a cache, it is volatile and will return to Tyk Cloud to get key data if it can’t find a reference there, which can happen if you restart the container.
1- If we restart the container, then we make an api request and we pass a correct key.
2- The Hybrid will not find the key in its cache and it will try to fetch from tyk cloud.
Should we get in this case a “Key not authorized” error?
Is there a way in hybrid config to make it rebuild its cache from tyk cloud whenever it gets restarted.
We need to avoid getting this error when the hybrid restarts.