Require valid clients for all audit events

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Security 2021-03-22
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We take a client pointer to our audit hooks but allow for it to be nullptr. Audit events are related to changes in storage, networking, or other stateful systems, thus we should always have at least a client if not an opCtx. We should invariant that the client exists and fix places where it does not. (Notably, logLogout fails to acquire the current client during client decoration destruction.)

            Assignee:
            Benjamin Caimano (Inactive)
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: