Remove magic link token from passwordless API response#119
Merged
Conversation
Add backup_codes_shown flag to user_mfa table. Backup codes are only returned on the initial setup request and marked as shown afterwards. Re-running setup will regenerate codes but not display them. Add a /mfa/rotate-backup-codes endpoint that requires current TOTP token to view new backup codes.
Prevent token leak by removing the raw passwordless token from the API response body. The token is still stored hashed in the database and can be verified via /auth/passwordless/verify. The response now only returns a generic success message.
Senthil455
commented
Jun 17, 2026
Senthil455
left a comment
Senthil455
left a comment
Owner
Author
There was a problem hiding this comment.
Simple fix that removes the token leak from the passwordless response. The token is still stored and verified correctly on the verify endpoint.
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.
Remove the raw passwordless token from the API response body to prevent token leakage. The token is still stored hashed in the database and verified via /auth/passwordless/verify. The response now only returns a generic success message.