Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14282

Investigate changes in SERVER-36263: Bypassing operation validation in applyOps should require special privilege

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0, 4.2.16, 4.0.27, 4.4.9
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: Mar16 - Mar23, ServerDocs2020: Mar23 - Mar30, ServerDocs2020: Mar30 - Apr06, ServerDocs2020: Apr6 - Apr13, ServerDocs2020: Apr13 - Apr20, ServerDocs2020: Apr20 - Apr27, ServerDocs2020: Apr27 - May4, ServerDocs2020: May4 - May11, ServerDocs2020: May11 - May18, ServerDocs2020: May18 - May25, ServerDocs2020: May25 - Jun1, ServerDocs2021: Aug3 - Aug10

      Description

      Description

      Downstream Change Summary

      We are adding a new privilege that must be acquired to be able to perform
      "applyOps" command.
      ActionType-> applyOps
      Resource-> cluster

      Description of Linked Ticket

      As of SERVER-25994, a user can run applyOps if they have the privileges to perform each individual operation specified in the the applyOps command. However, applyOps is more powerful than other commands in that it avoids certain input validation (see SERVER-27096SERVER-32941SERVER-32952, and SERVER-32305). This is done intentionally, since applyOps is supposed to behave similarly to oplog application, where the primary does all validation and the secondary applies the changes exactly as the primary specified without validation. This feature is important to products that mimic oplog application, such as mongomirror and mongorestore. However, users should not be able to bypass validation simply because they have permission to write to a collection. Instead, applyOps should require a special privilege for bypassing validation.

      We will create a new privilege bypassing system-level invariants in applyOps. Today, this privilege will be required in order to run applyOps at all, since we have not implemented a version of applyOps that performs validation. The privilege will be included in dbAdminAnyDatabase, which is included in the custom role atlasAdmin and the temporary user that we create for Live Imports (mongomirror).

      Scope of changes

      Add new privilege to https://docs.mongodb.com/manual/reference/privilege-actions/

      See what roles have this privilege and add the privilege to the corresponding roles on https://docs.mongodb.com/manual/reference/built-in-roles/.

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ian.fogelman Ian Fogelman
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Backlog - Core Eng Program Management Team Backlog - Core Eng Program Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                17 weeks, 4 days ago
                Date of 1st Reply: