On this page
db.updateRole()
On this page
Definition
db.
updateRole
( rolename, update, writeConcern )-
Updates a user-defined role. The
db.updateRole()
method must run on the role’s database.An update to a field completely replaces the previous field’s values. To grant or remove roles or privileges without replacing all values, use one or more of the following methods:
db.grantRolesToRole()
db.grantPrivilegesToRole()
db.revokeRolesFromRole()
db.revokePrivilegesFromRole()
Warning
An update to the
privileges
orroles
array completely replaces the previous array’s values.The
updateRole()
method uses the following syntax:db.updateRole( "<rolename>", { privileges: [ { resource: { <resource> }, actions: [ "<action>", ... ] }, ... ], roles: [ { role: "<role>", db: "<database>" } | "<role>", ... ], authenticationRestrictions: [ { clientSource: ["<IP>" | "<CIDR range>", ...], serverAddress: ["<IP>", | "<CIDR range>", ...] }, ... ] }, { <writeConcern> } )
The
db.updateRole()
method accepts the following arguments:Parameter Type Description rolename
string The name of the user-defined role to update. update
document A document containing the replacement data for the role. This data completely replaces the corresponding data for the role. writeConcern
document Optional. The level of write concern for the update operation. The writeConcern
document takes the same fields as thegetLastError
command.The
update
document specifies the fields to update and the new values. Each field in theupdate
document is optional, but the document must include at least one field. Theupdate
document has the following fields:Field Type Description privileges
array Optional. Required if you do not specify roles
array. The privileges to grant the role. An update to theprivileges
array overrides the previous array’s values. For the syntax for specifying a privilege, see theprivileges
array.roles
array Optional. Required if you do not specify privileges
array. The roles from which this role inherits privileges. An update to theroles
array overrides the previous array’s values.authenticationRestrictions
array Optional.
The authentication restrictions the server enforces on the role. Specifies a list of IP addresses and CIDR ranges users granted this role are allowed to connect to and/or which they can connect from.
New in version 3.6.
The
db.updateRole()
method wraps theupdateRole
command.
Roles
In the roles
field, you can specify both built-in roles and user-defined roles.
To specify a role that exists in the same database where db.updateRole()
runs, you can either specify the role with the name of the role:
"readWrite"
Or you can specify the role with a document, as in:
{ role: "<role>", db: "<database>" }
To specify a role that exists in a different database, specify the role with a document.
Authentication Restrictions
New in version 3.6.
The authenticationRestrictions
document can contain only the following fields. The server throws an error if the authenticationRestrictions
document contains an unrecognized field:
Field Name | Value | Description |
---|---|---|
clientSource |
Array of IP addresses and/or CIDR ranges | If present, when authenticating a user, the server verifies that the client’s IP address is either in the given list or belongs to a CIDR range in the list. If the client’s IP address is not present, the server does not authenticate the user. |
serverAddress |
Array of IP addresses and/or CIDR ranges | A list of IP addresses or CIDR ranges to which the client can connect. If present, the server will verify that the client’s connection was accepted via an IP address in the given list. If the connection was accepted via an unrecognized IP address, the server does not authenticate the user. |
Important
If a user inherits multiple roles with incompatible authentication restrictions, that user becomes unusable.
For example, if a user inherits one role in which the clientSource
field is ["198.51.100.0"]
and another role in which the clientSource
field is ["203.0.113.0"]
the server is unable to authenticate the user.
For more information on authentication in MongoDB, see Authentication.
Behavior
Replica set
If run on a replica set, db.updateRole()
is executed using majority
write concern by default.
Scope
Except for roles created in the admin
database, a role can only include privileges that apply to its database and can only inherit from other roles in its database.
A role created in the admin
database can include privileges that apply to the admin
database, other databases or to the cluster resource, and can inherit from roles in other databases as well as the admin
database.
Required Access
You must have the revokeRole
action on all databases in order to update a role.
You must have the grantRole
action on the database of each role in the roles
array to update the array.
You must have the grantRole
action on the database of each privilege in the privileges
array to update the array. If a privilege’s resource spans databases, you must have grantRole
on the admin
database. A privilege spans databases if the privilege is any of the following:
- a collection in all databases
- all collections and all database
- the
cluster
resource
You must have the setAuthenticationRestriction
action on the database of the target role to update a role’s authenticationRestrictions
document.
Example
The following db.updateRole()
method replaces the privileges
and the roles
for the inventoryControl
role that exists in the products
database. The method runs on the database that contains inventoryControl
:
use products
db.updateRole(
"inventoryControl",
{
privileges:
[
{
resource: { db:"products", collection:"clothing" },
actions: [ "update", "createCollection", "createIndex"]
}
],
roles:
[
{
role: "read",
db: "products"
}
]
},
{ w:"majority" }
)
To view a role’s privileges, use the rolesInfo
command.