Pain point · Permissions & security · Blocks work
JWT check fails on one second of clock skew
1 source thread · first seen 2019-05
Summary
A one second clock difference between Hasura and the Firebase token issuer causes tokens to be rejected as issued in the future, and the user asks for a leeway window.
- Affects
- Firebase auth users
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“I have an error cause by a clock skew of one second between my hasura server and my JWT service (Firebase)”