-
Notifications
You must be signed in to change notification settings - Fork 46
fix: add authentication and ownership checks to unauthenticated endpoints #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
memosr
wants to merge
2
commits into
circlefin:master
Choose a base branch
from
memosr:fix/missing-auth-multiple-endpoints
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This auth check can break the existing onboarding wallet provisioning path.
signUpActionand/auth/callbackcall this endpoint with server-sidefetch()and only aContent-Typeheader:app/actions/index.tscalls/api/wallet-set, then/api/walletapp/auth/callback/route.tscalls/api/wallet-set, then/api/walletThis route now reads the Supabase user from request cookies via
createSupabaseServerClient().auth.getUser(). I reproduced the relevant runtime boundary locally with Node server-sidefetch(): a request built with only{ "Content-Type": "application/json" }sends noCookieheader to the target server. With the current onboarding calls, this can hit the new401path before wallet-set creation. The same pattern applies to the new auth check inapp/api/wallet/route.ts.I would keep the endpoint auth hardening, but avoid routing the server-side onboarding flow through cookie-authenticated HTTP calls. A smaller fix would be to move wallet-set/wallet creation into a shared server helper used directly by sign-up/callback and by the API routes, or explicitly preserve the authenticated request cookies when these internal calls are made.
A regression test should cover: "new user sign-up/callback creates wallet set and wallet."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the thorough review, @Cassxbt! - You're absolutely right / the cookie-forwarding gap on server-side
fetch()would have broken new-user onboarding. Good catch.Refactored in 493a14a to follow your shared-helper suggestion:
lib/wallet-provisioning.ts(new) - single source of truth for Circle SDK wallet provisioning. Two exported functions:createWalletSet(entityName)— wrapscircleDeveloperSdk.createWalletSet+ DB persistcreateWallet(walletSetId, blockchain)— wrapscircleDeveloperSdk.createWallets+ DB persistapp/api/wallet-set/route.ts&app/api/wallet/route.tsapp/actions/index.ts(signUpAction) &app/auth/callback/route.tsfetch()calls to/api/wallet-setand/api/walletThis way:
Net change: +61 / -84 (less code, no inline duplication).
For the regression test you mentioned ("new user sign-up/callback creates wallet set and wallet"): happy to add one in a follow-up PR if you'd like — I noticed the repo doesn't currently have an integration test setup, so I left that out of this scope to keep the PR focused. Let me know if you want it included here instead.