The ID token is not yet valid. Make sure your computer’s time and time zone are both correct. Current epoch = 1689517128

0. The ID token is not yet valid. Make sure your computer’s time and time zone are both correct. Current epoch = 1689517128. The id_token was: {
   “aud”: “0xxxxb-461a-bbee-02f9e1bf7b46”,
   “iss”: “https://login.microsoftonline.com/ddffxxxxxx1-a52e-f96d02fed6b6/v2.0”,
   “iat”: 1689520008,
   “nbf”: 1689520008,
   “exp”: 1689523908,
   “aio”: “ATQAy/8TAAAAxxxKyHtFIBqtMZJV3h9hgp9YzUU9RxxxQp54mWpV/NZzV1d”,
   “name”: “System Administrator”,
   “oid”: “cb508935-ad4f-4224-8ea4-3504125ee313”,
   “preferred_username”: “admin@xxxx.onmicrosoft.com”,
   “puid”: “1003xx04”,
   “rh”: “0.AXwAvxxxltAv7WtpV3sATbjRpGu-4C-eG_e0a7AOg.”,
   “sub”: “Hb5J9zYpwc7xxx3W-qgJOfG8jURyjUxGBXQH1g”,
   “tid”: “ddff00bd-12xxxxxa52e-f96d02fed6b6”,
   “uti”: “dD3jVWxxxxpAA”,
   “ver”: “2.0”
   }

At times, my WSL started behaving cranky with the above message. It’s apparent there is some timing variation (synching issue) btw my laptop and azure svc.

To fix, I have to run $ hwclock -s

Set the System Clock from the Hardware Clock. The time read from the Hardware Clock is compensated to account for systematic drift before using it to set the System Clock. See the discussion below, under The Adjust Function.

You can read more about by typing $ man hwclock and also test by calling $ hwclock –test