Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-53962

Move UMC audit hooks to OpObservers

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0 Required
    • Component/s: Internal Code, Security
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change
    • Sprint:
      Security 2021-02-08, Security 2021-02-22

      Description

      We should consider moving the audit hooks from the User Management Commands to the AuthOpObserver, which would invoke them solely on primaries. When a primary performs a write to these system collections, either as a part of a User Management Command or as part of a CRUD operation, the hook will check whether the generated oplog event implies that an authorization audit event should be recorded. If yes and the current node is a primary, it will invoke the audit hook. Because primaries invoke OpObserves in the catalog layer while clients perform operations, the active OperationContext will contain the client's authentication and authorization state.

        Attachments

        1. log.json
          4 kB
        2. Results1.txt
          3 kB
        3. Results2.txt
          3 kB

          Issue Links

            Activity

              People

              Assignee:
              sergey.galtsev Sergey Galtsev
              Reporter:
              spencer.jackson Spencer Jackson
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: