Error occurred while verifying paramstimesigned is more than 1m0s ago - Expired token

Embedded Wallets (Web3Auth)
1

:classical_building: Content from Web3Auth Community

This topic was originally posted by shahbaz on 3/7/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.

Error occurred while verifying paramstimesigned is more than 1m0s ago

2

“Error occurred while verifying paramstimesigned is more than 1m0s ago 2022-02-24 13:46:05 +0000 UTC” error could be because:

  • JWT is expired.
  • The JWT’s exp field is less than the current time.
  • The JWT’s iat field is greater than 60s from current time.

Web3Auth accepts only those JWTs whose iat is less than the current time and is not greater than 60s from current time. Regardless of the exp field of the JWT.

  • In short, the JWT is considered expired if the iat is greater than 60s from the current time.
3

Hi @shahbaz ,

Is there a way for us to extend the 60s limit because it doesn’t fit our use-case. We can to authenticate the users later in out app and not within 60s.