-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[PM-28616] Add UsePhishingBlocker in the client against organization #17681
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
|
Claude finished @voommen-livefront's task —— View job Code Review CompleteI've reviewed the changes to add the SummaryThe PR successfully adds the FindingsFinding 1: Missing 💭 The test file Suggested fixIn ssoEnabled: false,
ssoMemberDecryptionType: MemberDecryptionType.MasterPassword,
usePhishingBlocker: false,Positive Observations
PR Metadata AssessmentThe PR title and description are clear and well-structured:
|
|
Great job! No new security vulnerabilities introduced in this pull request |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #17681 +/- ##
==========================================
- Coverage 41.56% 41.55% -0.01%
==========================================
Files 3553 3553
Lines 102367 102371 +4
Branches 15355 15357 +2
==========================================
- Hits 42547 42542 -5
- Misses 58027 58035 +8
- Partials 1793 1794 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|

🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-28616
📔 Objective
On the server side PR (bitwarden/server#6625) we add the
UsePhishingBlockerflag todbo.OrganizationIn this PR, we ensure that the
UsePhishingBlockerproperty is available in the Organization entity on the client side.📸 Screenshots
⏰ 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