-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[PM-18612] Consolidate all email OTP to use 6 digits #5967
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
New Issues (5)Checkmarx found the following issues in this Pull Request
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5967 +/- ##
==========================================
- Coverage 47.59% 47.59% -0.01%
==========================================
Files 1676 1676
Lines 74741 74737 -4
Branches 6753 6753
==========================================
- Hits 35574 35570 -4
Misses 37707 37707
Partials 1460 1460 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-18612
📔 Objective
Currently the base
EmailTokenProvider
uses 8 digits for the OTP, and theEmalTwoFactorTokenProvider
overrides this with 6.As we have more users using the
EmailTokenProvider
for New Device Verification, we have been asked to change this to 6 digits as well. This allows us to consolidate the implementation and not override any of the token parameters on the child class.The
EmailTokenProvider
is used:To improve clarity on why we are inheriting in the
EmailTwoFactorTokenProvider
, I added a comment to explain what it does relative to its base class. I did not elect to refactor this inheritance at this point.📸 Screenshots
otp_user_verification.mov
otp_new_device_verification.mov
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes