Current date\/time MUST be before the expiration date\/time listed in the 'exp' claim

Answered

Follow

New post

StingLikeABee

• June 10, 2016 07:23

Hello,

 

We have an integration using app users and starting last weekend (6/4/2016) we started seeing the error when trying to authenticate using JWT.  Its been running for a few months and we didn't see this error so I'm guessing something must have changed for creating the JWT claims, in particular the exp part the of the claim?  Any more insight as to the change and maybe a little more info about the error?

 

Thanks in advance!

0

• 

  Murtza

  • June 12, 2016 20:56

   

  This error happens when the Unix time on your local machine and the Box server are out of sync. 

   

  To fix this error, update the Unix time on your machine to match the Unix time from this site. Then retry your request to generate the App User access token.

   

  Please let me know if that fixes the error?

  0

  Comment actions Permalink
• 

  StingLikeABee

  • June 13, 2016 04:46

  Thanks Murtza

   

  I think that might do the trick.  I checked and the one server in question seems to be drifting about 45 seconds off from all of our others.  I've adjusted and will keep watch this week but my guess is that you nailed it.

   

   

  0

  Comment actions Permalink
• 

  romanApll

  • June 17, 2018 14:21

  Hello. I keep getting the same error nspite of time synchronization with time,gov, windows synchronization and etc. Do you have a normal way to access your api without this time checkings? Or can you guarantee that you sever time is correct?

  0

  Comment actions Permalink
• 

  dwrober

  • June 29, 2018 13:21

  I am having this issue currently as well on my local machine.  As far as I can tell, the current date/time is accurate.

  0

  Comment actions Permalink
• 

  dave_eos

  • July 19, 2018 10:31

  We're having this problem now after deploying. We deploy to Heroku. Maybe Box can sync its time with their servers instead?

  0

  Comment actions Permalink
• 

  dave_eos

  • November 06, 2018 11:27

  FYI, we are still having this problem. This is a quite a lot of trouble for us and no resolution. Must Box be so strict?

  0

  Comment actions Permalink

Please sign in to leave a comment.