Definition
revokePrivilegesFromRoleRemoves the specified privileges from the user-defined role on the database where the command is run. The
revokePrivilegesFromRolecommand has the following syntax:Tip
In the
mongoShell, this command can also be run through thedb.revokePrivilegesFromRole()helper method.Helper methods are convenient for
mongousers, but they may not return the same level of information as database commands. In cases where the convenience is not needed or the additional return fields are required, use the database command.{ revokePrivilegesFromRole: "<role>", privileges: [ { resource: { <resource> }, actions: [ "<action>", ... ] }, ... ], writeConcern: <write concern document>, comment: <any> } The
revokePrivilegesFromRolecommand has the following fields:FieldTypeDescriptionrevokePrivilegesFromRolestring
The user-defined role to revoke privileges from.
privilegesarray
An array of privileges to remove from the role. See
privilegesfor more information on the format of the privileges.writeConcerndocument
Optional. The level of write concern for the modification. The
writeConcerndocument takes the same fields as thegetLastErrorcommand.commentany
Optional. A user-provided comment to attach to this command. Once set, this comment appears alongside records of this command in the following locations:
mongod log messages, in the
attr.command.cursor.commentfield.Database profiler output, in the
command.commentfield.currentOpoutput, in thecommand.commentfield.
A comment can be any valid BSON type (string, integer, object, array, etc).
New in version 4.4.
Behavior
To revoke a privilege, the resource document pattern must match exactly the
resource field of that privilege. The actions field can be a
subset or match exactly.
For example, consider the role accountRole in the products
database with the following privilege that specifies the products
database as the resource:
{ "resource" : { "db" : "products", "collection" : "" }, "actions" : [ "find", "update" ] }
You cannot revoke find and/or update from just one
collection in the products database. The following operations
result in no change to the role:
use products db.runCommand( { revokePrivilegesFromRole: "accountRole", privileges: [ { resource : { db : "products", collection : "gadgets" }, actions : [ "find", "update" ] } ] } ) db.runCommand( { revokePrivilegesFromRole: "accountRole", privileges: [ { resource : { db : "products", collection : "gadgets" }, actions : [ "find" ] } ] } )
To revoke the "find" and/or the "update" action from the role
accountRole, you must match the resource document exactly. For
example, the following operation revokes just the "find" action
from the existing privilege.
use products db.runCommand( { revokePrivilegesFromRole: "accountRole", privileges: [ { resource : { db : "products", collection : "" }, actions : [ "find" ] } ] } )
Required Access
You must have the revokeRole action on the database a privilege targets in order to
revoke that privilege. If the privilege targets multiple databases or the
cluster resource, you must have the revokeRole action
on the admin database.
Example
The following operation removes multiple privileges from the
associates role in the products database:
use products db.runCommand( { revokePrivilegesFromRole: "associate", privileges: [ { resource: { db: "products", collection: "" }, actions: [ "createCollection", "createIndex", "find" ] }, { resource: { db: "products", collection: "orders" }, actions: [ "insert" ] } ], writeConcern: { w: "majority" } } )