Conversation
c90be14 to
5a50713
Compare
| )} | ||
| {disable2FAModalRevealed && ( | ||
| <DisableTwoStepAuthModal {...{ hideDisable2FAModal }} /> | ||
| <MfaGuard |
df95652 to
a175bc1
Compare
| }, | ||
| handler: async function (request) { | ||
| return routes | ||
| .find( |
There was a problem hiding this comment.
@MagentaManifold @nshirley @vpomerleau I like this approach for the simple reason that it doesn't corrupt the git history of the previous route handler and makes the diff nicer.
a95cc14 to
4b24f50
Compare
8b462c8 to
0244424
Compare
| }, | ||
| handler: async function (request) { | ||
| return routes | ||
| .find( |
There was a problem hiding this comment.
So, comments here are non-blocking.
But, I grabbed the branch and hit a but. The Change button is also prompting with the MfaGuard. And, if the token is expired (to where it should re-prompt) I just get an error 401. Looks like it's just not hitting the error boundary there. Maybe it's not intentional to have the change triggering this in this PR?
If it turns out to be a "me" issue then I'll update my review! Wanted to flag in case it is something actually broken and unintentional
I realized that the change was done in this pr so what I'm seeing is likely not from your pr
Because: - We want to require MFA when disabling 2FA This Commit: - Wraps the 2FA row's disable button with an MfaGuard component - Updates functional tests to supply MfaGuard's OTP code when required
Because
This pull request
Issue that this pull request solves
Closes: FXA-12230
Checklist
Put an
xin the boxes that applyScreenshots (Optional)
Please attach the screenshots of the changes made in case of change in user interface.
Other information (Optional)
A lot of tests 'disable 2FA' as part of the test tear down.