Repository navigation
Conversation
API ChangesNo changes. |
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.
Split from #302.
Problem
POST /1/auth/totp/loginissued a full session from just an email and a 6-digit TOTP code. No password was needed.verifyTotpchecked for a recent password onlyif (authenticator.isMfa), andenableTotpnever setsisMfa. The check never ran, so the authenticator app replaced the password instead of acting as a second factor.Fix
verifyTotpnow always callsverifyRecentPassword. The password must have been verified in the last 5 minutes (MFA_THRESHOLD), which the/auth/password/loginstep does before it asks for the TOTP code.Behaviour change
Tests
lastUsedAtassertion looks up the TOTP authenticator by type, because the user now has both a password and a TOTP authenticator.