-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-28337] Remove account recovery permission feature flag #6698
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
|
Great job! No new security vulnerabilities introduced in this pull request |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6698 +/- ##
==========================================
+ Coverage 53.63% 53.87% +0.23%
==========================================
Files 1926 1914 -12
Lines 85717 84944 -773
Branches 7686 7597 -89
==========================================
- Hits 45977 45760 -217
+ Misses 37967 37425 -542
+ Partials 1773 1759 -14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Claude finished @trmartin4's task —— View job Code Review for PR #6698 ✅Feature flag removal for account recovery permission Tasks
Overall Assessment: APPROVE 👍This PR correctly removes the No critical or blocking issues found. Detailed Findings📝 Finding 1: Obsolete Documentation Comment (Minor Cleanup)Location: The XML documentation comment states: /// <summary>
/// This logic has been flagged as part of PM-23174.
/// When removing the server flag, please also remove this test, and remove the FeatureService
/// dependency from this suite and the following test.
/// </summary>Recommendation: Remove this obsolete comment (lines 226-230). The FeatureService dependency has been removed as instructed, but the test itself should remain since it validates important security logic for the ManageResetPassword permission. The comment is now misleading. Severity: Low - Documentation cleanup 📝 Finding 2: Code Comment Reference to Removed FeatureLocation: The comment references the now-removed feature flag: async Task<bool> EvaluateHasManageResetPasswordPermission()
{
// PM-23174
// Determine if user has manage reset password permission...Recommendation: Remove or update the "PM-23174" reference since the flag is now permanently removed and this is the standard implementation. Severity: Technical Debt - Minor ❓ Finding 3: Additional Feature Flags RemovedLocation: The diff shows three feature flags were removed:
Question: Can you confirm that flags #2 and #3 came from the main branch merge (commit 039c0ae) and are intentional? Based on the commit history, this appears to be the case, but worth verifying. Security Analysis ✅Zero-Knowledge Compliance: No concerns. Changes maintain existing security logic. Access Control: The removal correctly preserves intended behavior:
No Security Regressions: The old conditional logic is completely removed, eliminating complexity and potential inconsistencies. Test Coverage Analysis ✅Appropriate Test Changes:
Remaining Tests Cover:
Coverage Assessment: Excellent - all critical paths remain tested. Code Quality Improvements 🎨This PR improves code quality by:
SummaryThe feature flag removal is complete, correct, and secure. The only items are minor documentation cleanup suggestions. Great job on a clean feature flag removal! 🌱 |

🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-28337
📔 Objective
Removes
pm-23174-manage-account-recovery-permission-drives-the-need-to-set-master-passwordfeature flag and flagged logic on the server. There was no flagged client-side logic for this feature.⏰ 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