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(auth): bind accessToken cookie + JWT to a 7-day TTL #13
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
Uh oh!
There was an error while loading. Please reload this page.
fix(auth): bind accessToken cookie + JWT to a 7-day TTL #13
Changes from all commits
ad431a1File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
Already addressed in the current revision — the comparison-based check has been replaced with an explicit type check exactly as suggested:
This decodes the incoming token's payload and requires
type === "transfer"for the route to proceed, rather than relying on the JWT-determinism heuristic that theexpiresAtfix invalidated. The existing test "should prevent token extension by rejecting JWT tokens" exercises this — a session JWT now reaches the route handler and gets rejected at the type check.The diff hunk Copilot is reading actually shows the fix already applied (the
-line is the old comparison, the+lines are the type check). Looks like a review-rendering issue where the bot is treating the pre-image of the hunk as active.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.
Good catch on the JWT-no-
expiresAtclaim — but worth flagging that this is a pre-existing upstream bug, not introduced by this PR. Theuser.getJwtToken(undefined, service)call on line 36 is unchanged; only the cookie'sexpiresline was modified.Net effect on exposure window:
So this PR actually shrinks the exposure ~13x. It doesn't introduce the mismatch.
Will file a separate follow-up to pass
expiresintogetJwtTokenat this call site (matching the pattern already used inmiddlewares/authentication.tsandutils/authentication.ts). Keeping this PR scoped to cookie TTL only.Uh oh!
There was an error while loading. Please reload this page.