[DOCS-13333] Investigate changes in SERVER-45038: Add privilege actions for getDefaultRWConcern and setDefaultRWConcern commands Created: 09/Jan/20  Updated: 13/Nov/23  Resolved: 01/May/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-45038 Add privilege actions for getDefaultR... Closed
Duplicate
Related
related to DOCS-13332 Investigate changes in SERVER-43723: ... Closed
related to DOCS-13345 Investigate changes in SERVER-45098: ... Closed
Participants:
Days since reply: 3 years, 40 weeks, 5 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

This ticket added two new auth actions, getDefaultRWConcern and setDefaultRWConcern for the commands to get and set the default read/write concern. The built in role clusterMonitor has the getDefaultRWConcern action (and any roles that encompass clusterMonitor) and the built in role clusterManager has both the getDefaultRWConcern and setDefaultRWConcern actions (and any roles encompassing clusterManager).

Description of Linked Ticket

Create and add privilege actions for getDefaultRWConcern and setDefaultRWConcern on both mongos and mongod.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Kay Kim (Inactive) [ 01/May/20 ]

Was done as part of DOCSP-7544

Generated at Thu Feb 08 08:07:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.