asgardeo / asgardeo-auth-react-sdk

To maintain the implementation of Asgardeo React authentication SDK

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

YOUR CLOCK IS INVALID during the login issue

lpastor74 opened this issue · comments

Describe the issue:

During the login Im getting the following error

YOUR CLOCK IS INVALID !
It looks like your computer’s date and time is incorrect. Please validate and try again

tried with latest sample application with same result!!!
Screen Shot 2023-05-08 at 8 50 48 AM

How to reproduce:
I have following the sample application installation.
Downloaded the React sample app. Unzip it.
npm install
result:

npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 676 packages, and audited 677 packages in 21s

91 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

- changed the clinet ID in base URL in config.json
npm start
result:

> @asgardeo/react-app@2.0.4 start
> webpack-dev-server --mode development --hot --open

<i> [webpack-dev-server] Generating SSL certificate...
<i> [webpack-dev-server] SSL certificate: /Users/laslopastor/Documents/WSO2/presentations/TimeStamps/ASGARDIO/REACT/react_may_two/node_modules/.cache/webpack-dev-server/server.pem
<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: https://localhost:3000/, https://127.0.0.1:3000/
<i> [webpack-dev-server] Content not from webpack is served from '/Users/laslopastor/Documents/WSO2/presentations/TimeStamps/ASGARDIO/REACT/react_may_two/dist' directory
<i> [webpack-dev-server] 404s will fallback to '/index.html'
asset main.js 2.85 MiB [emitted] (name: main) 1 related asset
asset 99731ec2aabea45c8355.ico 15 KiB [emitted] [immutable] [from: src/favicon.ico]
asset index.html 1.25 KiB [emitted]
orphan modules 1.72 MiB [orphan] 796 modules
runtime modules 27.5 KiB 14 modules
cacheable modules 2.55 MiB
  modules by path ./node_modules/ 2.47 MiB 188 modules
  modules by path ./src/ 79.5 KiB
    modules by path ./src/pages/*.tsx 28.4 KiB 5 modules
    modules by path ./src/components/*.tsx 7.47 KiB 3 modules
    modules by path ./src/*.tsx 2.56 KiB 2 modules
    modules by path ./src/*.css 12.6 KiB 2 modules
    modules by path ./src/images/*.png 25.8 KiB 2 modules
    + 3 modules
webpack 5.82.0 compiled successfully in 2491 ms

go to https://localhost:3000/

login with user name and password :

result

YOUR CLOCK IS INVALID !
It looks like your computer’s date and time is incorrect. Please validate and try again

We had a look at this issue. It looks like Laslo's machines date / time and time zone is correct. However it keeps happening from his machine while the same is working in other machines.

Also we tried to add clockTolerance config as well and it didn't work either.

Had a call with @brionmario and discussed to add more logs to the react sample to see what goes wrong as the console / browser logs were not conclusive enough on what's going on.

@pandukakarunasena could you please update the issue with the latest status?

Steps to verify

  • Download the react sample application.
  • Unzip the downloaded pack.
  • Run npm install.
  • Change the system time to a past Date and time
  • Try to log in with a username and password.
  • An Error page should be displayed signifying a clock validation

Furthermore, do the following to check for the issuer claim validation failure.

  • Add the base URL with a slash at the end in the app configurations.
    "baseUrl": "https://api.asgardeo.io/t/strb/"
  • An error page should be displayed signifying the issuer claim validation failure.

Verified the fix.

Untitled.mp4