Refine 2FA to enterprise-grade - #102
Merged
Merged
Conversation
- Hide recovery codes after setup; show them once (after enable/regenerate or a password-confirmed reveal), never on every page load - Require the account password for all sensitive 2FA actions (enable, disable, view codes, regenerate) via password-confirm modals - Add copy/download and an "I have saved my recovery codes" acknowledgment on the one-time reveal - Drive 2FA management through password-gated SettingsController routes delegating to Fortify's Action classes, avoiding the password.confirm middleware POST/DELETE redirect-drop - Gate Fortify's built-in 2FA routes as defense-in-depth (confirmPassword => true) and add the confirm-password view - Update and extend the 2FA test suite (16 tests)
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.
This fixes #99.