feat: user wallet linking, JWT auth middleware, and delivery schema updates - #86
Open
G-ELM wants to merge 4 commits into
Open
feat: user wallet linking, JWT auth middleware, and delivery schema updates#86G-ELM wants to merge 4 commits into
G-ELM wants to merge 4 commits into
Conversation
Allows a Stellar wallet public key to be linked to a user profile, enforced unique and format-validated at the schema level.
Extracts the bearer token from the Authorization header, verifies its signature, and attaches the decoded payload to req.user.
Validates the Stellar public key with StrKey before persisting it to the authenticated user's profile, guarding against duplicate wallet links across accounts. Also exposes userId on the authMiddleware payload type to match the JWT shape issued at login.
…very schema sender/recipient reference the User schema so deliveries can be resolved back to system users; contractId tracks the on-chain Soroban escrow contract for a delivery, and metadata holds free-form extra data.
|
@G-ELM Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Summary
walletAddressfield to the User schema for linking a Stellar wallet to a profile, with format validation and a unique/sparse index.authMiddleware.ts: verifies the Bearer JWT from the Authorization header and attaches the decoded payload toreq.userfor protected routes.PUT /api/v1/users/walletto link/update a user's Stellar wallet address, validating the public key withStrKey.isValidEd25519PublicKeyand rejecting wallets already linked to another account.sender/recipient(ObjectId refs toUser),contractId(on-chain Soroban escrow contract id), andmetadata(free-form extra data).Changes
src/interfaces/IUser.ts,src/models/User.ts—walletAddressfieldsrc/middlewares/authMiddleware.ts— JWT verification middlewaresrc/validators/userValidator.ts,src/controllers/userController.ts,src/routes/userRoutes.ts,src/routes/index.ts— wallet-linking endpointsrc/models/Delivery.ts—sender,recipient,contractId,metadatafieldsCloses #8
Closes #11
Closes #12
Closes #14