Hasura JWTIssuedAtFuture Error

[shihab-geo]

I have developed the JWT token generator using Nodejs in my Local Machine by following Hasura's JWT principle from the Doc. I am getting the token result properly.

{ "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJodHRwczovL2hhc3VyYS5pby9qd3QvY2xhaW1zIjp7IngtaGFzdXJhLWFsbG93ZWQtcm9sZXMiOlsiYWRtaW4iXSwieC1oYXN1cmEtZGVmYXVsdC1yb2xlIjoiYWRtaW4iLCJYLUhhc3VyYS1Vc2VyLUlkIjoiMTIzIn0sImlhdCI6MTY3OTM4MTY3MiwiZXhwIjoxNjc5MzgxNzkyfQ.61iK6o9g4kjmLUpES03W9_AJbrHHtnmzzxs8DCGsxtE" }

Hasure Image is hasura/graphql-engine:latest

Hasura Engine is running in a docker container in a Linux-hosted server. And I have added the HASURA_GRAPHQL_ADMIN_SECRET and HASURA_GRAPHQL_JWT_SECRET env as well. Note that The Linux-hosted server time and the Hasura docker container time are the same.

But the problem is after putting the generated token in the Hasura API endpoint, I am getting the following error:
"errors": [ { "extensions": { "code": "invalid-jwt", "path": "$" }, "message": "Could not verify JWT: JWTIssuedAtFuture" } ]

But, after some time I could get the result properly from the same Hasura API using the same Token.

I don't know why this weird thing is happening.

It would be helpful to give me a solution.

[shihab-geo]

I had solved my issue.

I figured out that the time of my Hasura-engine docker container was 2 minutes slower than my server time.

So I had delayed 2 minutes in the 'iat' from my JWT generator logic.