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

users on mongos should always be able to run currentOp and killOp on their own operations

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.3.10
    • Component/s: Security, Sharding
    • Labels:
    • Sharding

      SERVER-17856 added support for users on mongod running currentOp and killOp against operations they themselves had started.
      From that ticket:

      Both the inprog (currentOp) and killop (killOp) roles are granted at the cluster resource level, which makes them an all-or-none condition (I believe).

      Use case:

      Give developers access to a database with restricted access (basically read-only, non-administrative authority). However because they are given the ability to execute queries, it would be nice if they had the ability to kill any process that were executed by them. Some tools, such as Aqua Data Studio, utilize the killOp command to terminate any queries executed from their query window, however this functionality only works for individuals with administrative roles.
      One solution would be to permit killOp command to be permissioned to allow a user to kill his own processes but no other.

      Perhaps even just a single new role (userKillOp?) could suffice.

      Though harder to achieve, this functionality should work on mongos as well.

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            spencer.jackson@mongodb.com Spencer Jackson
            2 Vote for this issue
            7 Start watching this issue


                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.