You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
When a user signs into the Dapp the authentication token is created. And it is only valid for the network user is currently on. If the user switches networks the token is no longer valid (from Rinkeby to Mainnet for example), but Dapp still shows user as signed in. Services that verify the token (like growth server) will fail all the requests.
When the Dapp loads it should verify the stored token and sign the user out if the token is not valid.
The text was updated successfully, but these errors were encountered:
When a user signs into the Dapp the authentication token is created. And it is only valid for the network user is currently on. If the user switches networks the token is no longer valid (from Rinkeby to Mainnet for example), but Dapp still shows user as signed in. Services that verify the token (like growth server) will fail all the requests.
When the Dapp loads it should verify the stored token and sign the user out if the token is not valid.
The text was updated successfully, but these errors were encountered: