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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor the mailer content to specify the MFA implementation used (TOTP) #3903
Refactor the mailer content to specify the MFA implementation used (TOTP) #3903
Conversation
1fef7e9
to
c7f45f9
Compare
Thanks for the PR. Change looks good to me, but since I'm not native English speaker I'll leave this open for additional reviewer. |
Codecov Report
@@ Coverage Diff @@
## master #3903 +/- ##
=======================================
Coverage 98.79% 98.79%
=======================================
Files 216 216
Lines 5391 5391
=======================================
Hits 5326 5326
Misses 65 65
|
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.
馃憤 Looks good! Thanks for helping to refactor this George.
I'm torn on the email heading title as well. Not a fan of the double acronyms. TOTP is too long to spell out, I think we can still work with spelling out MFA. Here are some alternatives I thought of. What do you think about these options?
- TOTP Multi-factor Authentication Enabled
- Multi-factor Authentication Enabled: TOTP
- MFA Enabled: One-Time Password
- I know I dropped the "Time-Based" part in this title. I figured it'd be an acceptable in-between since the email body notes that it's TOTP.
Email subject title changed to: After some more discussions with Betty/Jenny, the rest of the email looks like this: let me know if this looks good! cc: @bettymakes |
Changes look good! 馃殌 |
5fa5de4
to
220ec1a
Compare
Update the mailer tests for the mfa to totp refactor Rename other locales with the mfa to totp refactor Update the wording to include 'authenticator app'
220ec1a
to
e024593
Compare
What problem are you solving?
Closes https://github.com/Shopify/ruby-dependency-security/issues/331
Refactored the email content to specify the MFA implementation used (TOTP)
What should reviewers focus on?
Not the biggest fan of the lengthiness of some of the content:
ie. the email subject
and the content body
but also just didn't like the way TOTP MFA looked (acronym overload), but I would be okay to change some/both of these if there any suggestions 馃槃
Testing 馃帺
Borrowing the testing instructions from a previous PR within the same section of code (thanks @garyhtou):
Can also view the updated mailers individually through http://localhost:3000/rails/mailers