The dashboard fails to open if the local wall clock is not correct

[giorio94]

Describe the bug
It is impossible to access the LiqoDash in case the local time (i.e. wall clock) is not configured correctly (e.g. one hour back). This is probably related to the validity of the log-in token. However, the dashboard remains stuck displaying the loading animation, and no error messages are displayed to the user pointing out the problem.

To Reproduce
Steps to reproduce the behavior:

1. Change the local time to an incorrect value (e.g. one hour back).
   E.g., from a CrownLabs VM:

   sudo timedatectl set-ntp 0
   sudo timedatectl set-time hh:mm
   

2. Go to beta.crownlabs.polito.it
3. Log-in as usual
4. The dashboard remains stuck in the callback (i.e. displaying the loading animation)

Expected behavior
The dashboard should either work correctly or a clear error message should displayed to the user.

Additional context

• Reproduced with both Firefox and Chrome
• The same bug affects also the CrownLabs dashboard
• Checking the developer tools, an error similar to the following is shown in the console:

  Error: iat is in the future: 1607938330
      at Function.e.validateJwtAttributes (bundle.js:90)
      at bundle.js:47