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

Docs for SERVER-28260: Create a killAnyCursor privilege

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.1, 3.6.3
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      Scope of changes:

      This change adds authorization checks to the killCursors command.
      Previously, any user could kill any cursor provided that they knew (or could guess) the cursor ID. With this change, the cursor must have been created by at least one of the currently authenticated users, otherwise killing the cursor will fail.

      Additionally, previous behavior would always result in an "ok" response with detail in the "cursorsKilled", "cursorsAlive", "cursorsNotFound" fields. With this change, authorization is checked before any kills are executed, and if any of the authorization checks fails, then no kills will occur and the response will indicate failure (ErrorCodes::Unauthorized). Similarly, if a cursor can not be found during an authorization check, then the entire transaction will fail without any kills being carried out.

      Drivers should be aware of the change in failure modes.
      Documentation should reflect the additional coAuthorization checks.

      Impact to other docs outside of this product:

      MVP:

      Resources:

      Engineering Ticket Description:

      A ClientCursor is associated with the set of users that were authenticated when it was created.
      A killCursors should only succeed if the intersection of currently authenticated users and the set of users associated with the ClientCursor is nonempty (or the set of users associated with the ClientCursor is empty), or if the user has the killAnyCursor privilege for that collection.

            Assignee:
            allison.moore@mongodb.com Allison Reinheimer Moore
            Reporter:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              5 years, 44 weeks, 1 day ago