Skip to main content

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!


 


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?



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.

 

 



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?



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



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



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?



Reply