Repository navigation
feat(nextjs): confirm cross-device magic links and move to @seamless-auth/nextjs 0.5 - #124
Merged
Merged
Conversation
Handle the auth server's 409 confirmation_required answer on the verify page: show the requesting device class and time, approve through confirmMagicLink (or a POST through /auth on older SDKs), or decline without side effects.
React 0.16's authorizedFetch refuses a path when apiHost is empty, which breaks the starter's same-origin calls to its own API.
This was referenced Oct 18, 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
1 participant
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.
Part of the v0.19 security release (fells-code/seamless-auth-api#385). Merge before fells-code/seamless-auth-api#449: its conformance run builds the Next.js starter from this repo's main and lockfile, and the same-browser magic link case needs the 0.5 adapter.
What
VerifyMagicLinkhandles the auth server's409 confirmation_required: it names the requesting device and time, and offers "Yes, sign in that device" (confirms viaclient.confirmMagicLinkwhen the SDK has it, otherwisePOST /auth/magic-link/verify/{token}/confirm) or "No, this wasn't me" (signs nothing in). Reviewed in the private advisory fork@seamless-auth/nextjs^0.4.0 to ^0.5.0, which forwards the browser's pre-auth token on verify so a link opened in the requesting browser signs in directly@seamless-auth/reactstays on ^0.15.2 (0.15.3): 0.16'sauthorizedFetchrefuses every path whenapiHostis empty, which broke the starter's/api/beta-userscall in the first conformance run. Tracked in fix(client): authorizedFetch refuses every path when apiHost is empty (same-origin apps) seamless-auth-react#188; the bump follows in chore: move the templates to @seamless-auth/react 0.16 and react-native 0.3 #123 once it is fixedAGENTS.mdnote; two minor changesetsChecks
templates/fullstack/nextjs:npm run check(tsc, eslint, prettier, vitest): 10 files, 61 tests pass;npm run build: passnpm run validateandnpm run format:check: pass