Web3 Login
A basic app to showcase connecting to a web3 wallet and signing a message to gain access to a protected page.
How It Works
The following steps describe the overall web3 login flow:
- The web application requests a wallet connection to one or more accounts
- The web application prepares a plain-text message and sends a signing request to the wallet
- Note: The current web app implementation assumes its always the first connected account is the one doing the signing. This can be easily modified such that the user selects the account that they want to sign the message with from a dropdown.
- Once the signature is obtained, it is sent along with the plain-text message and the account address to the API for verification. If the verification succeeds, a session cookie (JWT) is sent back from the API and stored in the browser locally.
- The user is redirect to the protected page
- The protection referred to here is at the UI / frontend level. This is done for UX purposes and doesn’t actually protect any secure resources (that’s on the API in Step 5 below).
- A secret value is requested from the API (which verifies the session cookie) and responds back to the UI if the token is valid.
Source Code
