TypeError: Not a Buffer about google-auth-library-nodejs HOT 5 CLOSED

In your case, how old was a "really old token"? I'm getting this error with an id token that was about 2 days old. Guess I'm not really sure how long they are supposed to last. The error did go away when I generated a new id token (signed out/signed back in) and used that with veryifyIdToken.

from google-auth-library-nodejs.

I don't recall right now, but I think that if you try to use a token that it's a day old you should get this error.

from google-auth-library-nodejs.

In the same verifyIdToken call, I'm now getting errors like "Token used too late, 1449031980.079 > 1449029024". I'm not sure if there is some variability in what gets returned from Google's servers, or if some change occurred to those servers.

I think these numbers are referring to the "exp" field of the IdToken, which has the definition:
"The time the ID token expires, represented in Unix time (integer seconds)."
(https://developers.google.com/identity/protocols/OpenIDConnect#obtainuserinfo)

I'll have to see if I can get the IdToken exp field immediately after obtaining the IdToken and convert the Unix time to a h/m/s time.

from google-auth-library-nodejs.

That is the expected behavior. If a token has expired, then you'll recieve that error. The issue that I'm describing is when instead of getting the correct error (Token userd too late) the pemVerify.verify call throws an error.

from google-auth-library-nodejs.

That error is to be expected if the token actually expired (You should check the expires_in field if there is any in your response). The issue I'm describing is that instead of getting the correct error (Token used too late) the perVerify.verify call throws an error due to the issue explained above.

If you're getting "Token used too late" you should refresh your access tokens.

from google-auth-library-nodejs.