Update new URL and method for backend verification#2901
Merged
yashovardhan merged 2 commits intomainfrom May 10, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
alexandratran
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix missing issuer and audience validation in JWKS-based JWT verification examples across the Embedded Wallets documentation. Without these checks, a token signed by Web3Auth for any other project passes signature verification, enabling cross-project token reuse against backends that identify users by userId, email, or authConnectionId.
Note
Low Risk
Low risk documentation-only change, but it updates security-critical guidance; incorrect values could cause token verification failures or misconfiguration if not reviewed carefully.
Overview
Updates Embedded Wallets docs to require
issuerandaudiencevalidation in all JWKS-based JWT verification examples, and explains the cross-project token reuse risk whenaudis not checked.Refreshes examples and troubleshooting to use the correct endpoints/issuers (e.g.,
https://api-auth.web3auth.io/jwksfor social logins andhttps://authjs.web3auth.io/jwksfor external wallets), and alignsjsonwebtoken/josesnippets to passalgorithms: ['ES256'],issuer, andaudienceconsistently.Reviewed by Cursor Bugbot for commit 86d91b2. Bugbot is set up for automated code reviews on this repo. Configure here.