# Auth0 generates a token which is signed a second in the future "iat" is incorrect

**URL:** <https://community.auth0.com/t/auth0-generates-a-token-which-is-signed-a-second-in-the-future-iat-is-incorrect/23046>\
**Category:** JWT.io\
**Tags:** jwt\
**Created:** [March 24, 2019, 11:17pm UTC](https://community.auth0.com/t/auth0-generates-a-token-which-is-signed-a-second-in-the-future-iat-is-incorrect/23046 "2019-03-24T23:17:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sethu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sethu/32/11987_2.png) [@Sethu](https://community.auth0.com/u/Sethu)\
**Post date:** [March 24, 2019, 11:17pm UTC](https://community.auth0.com/t/auth0-generates-a-token-which-is-signed-a-second-in-the-future-iat-is-incorrect/23046/1 "2019-03-24T23:17:49Z")

</div>

I am developing an application locally,.In the sense my API server is running locally. I am running an ‘implicit flow’ authentication and passing the access token obtained from Auth0 down to the API. The API rejects the token saying its signed in the future.

Exact exception message “Caused by: com.auth0.jwt.exceptions.InvalidClaimException: The Token can’t be used before **Mon Mar 25 10:07:23 AEDT 2019.** ”

The above log message is printed at this time: **2019-03-25 10:07:22.103** DEBUG 2657 — [nio-8080-exec-2] o.s.s.w.a.ExceptionTranslationFilter : Authentication exception occurred; redirecting to authentication entry point

I am not sure what is happening. This used to happen once in a while and I ignored it. But now it’s happening consistently and I am unable to proceed. Please help.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [April 4, 2019, 10:21am UTC](https://community.auth0.com/t/auth0-generates-a-token-which-is-signed-a-second-in-the-future-iat-is-incorrect/23046/3 "2019-04-04T10:21:33Z")

</div>

You should ensure that your local servers are configured with the correct date/time settings and in addition they should automatically synchronize from a trusted source (see [Network Time Protocol - Wikipedia](https://en.wikipedia.org/wiki/Network_Time_Protocol)).

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [September 2, 2019, 8:34am UTC](https://community.auth0.com/t/auth0-generates-a-token-which-is-signed-a-second-in-the-future-iat-is-incorrect/23046/4 "2019-09-02T08:34:07Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.