[SERVER-63175] Populate WriteBlockBypass in command dispatch Created: 01/Feb/22  Updated: 29/Oct/23  Resolved: 16/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0-rc1

Type: Task Priority: Major - P3
Reporter: Spencer Jackson Assignee: Gabriel Marks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-60657 Create Feature flag for PM-2584 Closed
depends on SERVER-63173 Create WriteBlockBypass decoration on... Closed
depends on SERVER-63174 Add "mayBypassWriteBlockingMode" meth... Closed
is depended on by SERVER-63177 Make mongos command dispatch install ... Closed
Duplicate
duplicates SERVER-63178 Make mongod override WriteBlockBypass... Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2022-02-21
Participants:

 Description   

During command dispatch, we should detect whether the AuthorizationSession believes the active Client is authorized to bypass write blocking mode. If either the client is authorized, or the client is a DBDirectClient, command dispatch should activate the WriteBlockBypass attached to the OperationContext.

The WriteBlockBypass should always be active if the feature flag is enabled.



 Comments   
Comment by Githook User [ 16/Feb/22 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-63175 Conditionally activate WriteBlockBypass in command dispatch
Branch: master
https://github.com/mongodb/mongo/commit/87ff8583b5348475a8506e268e13a126be35e531

Generated at Thu Feb 08 05:57:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.