Clock problem on MIEMIS server causes google redential login to fail

The MIEMIS Server reports time approx 30 minutes ahead of actual time.

‌

This time is synchronized to the HyperV somehow, and cannot be manually changed ( if you do, it just reverts back to its fualty setting in a few seconds)

‌

google cloud login reports this error:

message=Error:"invalid_grant", Description:"Invalid JWT: Token must be a short-lived token (60 minutes) and in a reasonable timeframe. Check your iat and exp values and use a clock with skew to account for clock differences between systems.", Uri:""

see stackoverflow.com/questions/36189612/token-must-be-a-short-lived-token-and-in-a-reasonable-timeframe

which all confirms the time lag being the culprit.

Comments (2)