Conversation
|
Great job! No new security vulnerabilities introduced in this pull request |
|
Claude finished @harr1424's task in 1m 18s —— View job Code Review: PM-31787 - Users can access the sends after the limit was reachedSummaryThis PR fixes a bug where authenticated users could access Sends after the access limit was reached. The fix correctly differentiates access counting behavior between Text and File Sends:
Status: ApprovedAll previous findings have been addressed:
What Looks Good
🤖 Generated with Claude Code |
src/Core/Tools/SendFeatures/Commands/Interfaces/INonAnonymousSendCommand.cs
Show resolved
Hide resolved
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6958 +/- ##
==========================================
- Coverage 60.27% 56.25% -4.02%
==========================================
Files 1982 1983 +1
Lines 87653 87692 +39
Branches 7816 7825 +9
==========================================
- Hits 52830 49331 -3499
- Misses 32904 36531 +3627
+ Partials 1919 1830 -89 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…fter-the-limit-was-reached
mcamirault
left a comment
There was a problem hiding this comment.
One tiny suggested cleanup but otherwise looks good!
src/Core/Tools/SendFeatures/Commands/NonAnonymousSendCommand.cs
Outdated
Show resolved
Hide resolved
…mit-was-reached' of github.com:bitwarden/server into PM-31787-Defect-Users-can-access-the-sends-after-the-limit-was-reached merge latest from main
|




🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-31787
📔 Objective
The new non-anonymous send access endpoints introduced flawed handling of Send access count enforcement. This PR restores parity between how Send access count is handled by these new endpoints with the prior anonymous endpoints:
Additional logic was added to short circuit the Send access request if any of the following are true for a given send: