Closed taka-oyama closed 8 months ago
We are aware of this. The internal team for Auth is working on fixing it.
Thank you for providing context. I have been told that this has been fixed and the logs show that error has not occurred since Feb 22. Closing.
Environment details
We are seeing the following error occur randomly throughout the day (~20 per day) in production.
I tried to reproduce this error by not sending the credentials by returning an empty array here. Unfortunately, I got a slightly different error which contained more context in the
details
section (see below).I then tried returning an expired token but that also resulted in a different message (see below).
So I have not been able to reproduce the error locally.
I also want to note that I added a customized
FetchAuthTokenCache
and deployed it to production to see if the token was actually being returned and did confirm that theaccess_token
did exist and was NOT expired.What I fail to understand is that when we deployed the customized
FetchAuthTokenCache
, we saw fewer errors throughout the day (~1 per day) even though no data is being altered. The error rate went back up again once we've reverted the code a week later.I'm wondering if it's a similar case to https://github.com/grpc/grpc/issues/15441?
Below is the customized
FetchAuthTokenCache