On this page本页内容
db.updateUser( username, update, writeConcern )
Updates the user's profile on the database on which you run the method. 更新运行该方法的数据库上的用户配置文件。An update to a field completely replaces the previous field's values. 字段的更新将完全替换上一个字段的值。This includes updates to the user's 这包括对roles array.roles角色数组的更新。
When you update the 更新roles array, you completely replace the previous array's values. roles数组时,将完全替换上一个数组的值。To add or remove roles without replacing all the user's existing roles, use the 要添加或删除角色而不替换用户的所有现有角色,请使用db.grantRolesToUser() or db.revokeRolesFromUser() methods.db.grantRolesToUser()或db.revokeRolesFromUser()方法。
The db.updateUser() method uses the following syntax:db.updateUser()方法使用以下语法:
Starting in version 4.2 of the 从mongoshell的4.2版开始,您可以将mongo shell, you can use the passwordPrompt() method in conjunction with various user authentication/management methods/commands to prompt for the password instead of specifying the password directly in the method/command call. passwordPrompt()方法与各种用户身份验证/管理方法/命令结合使用,提示输入密码,而不是直接在方法/命令调用中指定密码。However, you can still specify the password directly as you would with earlier versions of the 但是,您仍然可以像使用早期版本的mongo shell.mongoshell那样直接指定密码。
db.updateUser( "<username>", { customData : { <any information> }, roles : [ { role: "<role>", db: "<database>" } | "<role>", ... ], pwd: passwordPrompt(), // Or "<cleartext password>" authenticationRestrictions: [ { clientSource: ["<IP>" | "<CIDR range>", ...], serverAddress: ["<IP>", | "<CIDR range>", ...] }, ... ], mechanisms: [ "<SCRAM-SHA-1|SCRAM-SHA-256>", ... ], passwordDigestor: "<server|client>" }, writeConcern: { <write concern> } )
The db.updateUser() method has the following arguments.db.updateUser()方法有以下参数。
username | string | |
update | document | |
writeConcern | document |
|
The update document specifies the fields to update and their new values. update文档指定要更新的字段及其新值。All fields in the update document are optional, but must include at least one field.update文档中的所有字段都是可选的,但必须至少包含一个字段。
The update document has the following fields:update文档包含以下字段:
customData | document | |
roles | array | roles array overrides the previous array's values.roles数组的更新将覆盖上一个数组的值。
|
pwd | string |
|
authenticationRestrictions | array | |
mechanisms | array |
|
passwordDigestor | string |
Available values are:
"server". "server"。"client"."client"。
|
In the 在roles field, you can specify both built-in roles and user-defined roles.roles字段中,可以指定内置角色和用户定义的角色。
To specify a role that exists in the same database where 要指定存在于运行db.updateUser() runs, you can either specify the role with the name of the role:db.updateUser()的同一数据库中的角色,可以使用角色名称指定该角色:
"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.要指定存在于其他数据库中的角色,请使用文档指定该角色。
The authenticationRestrictions document can contain only the following fields. authenticationRestrictions文档只能包含以下字段。The server throws an error if the 如果authenticationRestrictions document contains an unrecognized field:authenticationRestrictions文档包含无法识别的字段,则服务器会引发错误:
| Field Name | ||
|---|---|---|
clientSource | ||
serverAddress |
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.clientSource字段为["198.51.100.0"]的一个角色和clientSource字段为["203.0.113.0"]的另一个角色,则服务器无法对该用户进行身份验证。
For more information on authentication in MongoDB, see Authentication.有关MongoDB中身份验证的更多信息,请参阅身份验证。
The db.updateUser() method wraps the updateUser command.db.updateUser()方法包装updateUser命令。
If run on a replica set, 如果在副本集上运行,db.updateUser() is executed using "majority" write concern by default.db.updateUser()在默认情况下使用"majority"写入关注点执行。
By default, 默认情况下,db.updateUser() sends all specified data to the MongoDB instance in cleartext, even if using passwordPrompt(). db.updateUser()将所有指定的数据以明文形式发送到MongoDB实例,即使使用passwordPrompt()。Use TLS transport encryption to protect communications between clients and the server, including the password sent by 使用TLS传输加密保护客户端和服务器之间的通信,包括db.updateUser(). db.updateUser()发送的密码。For instructions on enabling TLS transport encryption, see Configure 有关启用TLS传输加密的说明,请参阅为TLS/SSL配置mongod and mongos for TLS/SSL.mongod和mongos。
MongoDB does not store the password in cleartext. MongoDB不以明文形式存储密码。The password is only vulnerable in transit between the client and the server, and only if TLS transport encryption is not enabled.只有在客户端和服务器之间的传输过程中,并且只有在未启用TLS传输加密时,密码才会受到攻击。
You must have access that includes the 为了更新用户的角色数组,您必须具有包括所有数据库上的revokeRoleaction on all databases in order to update a user's roles array.revokeRole操作的访问权限。
You must have the 必须对角色的数据库执行grantRole action on a role's database to add a role to a user.grantRole操作才能向用户添加角色。
To change another user's 要更改另一个用户的pwd or customData field, you must have the changePassword and changeCustomDataactions respectively on that user's database.pwd或customData字段,必须在该用户的数据库上分别具有changePassword和changeCustomData操作。
To modify your own password and custom data, you must have privileges that grant 要修改您自己的密码和自定义数据,您必须具有分别对用户数据库授予changeOwnPassword and changeOwnCustomData actions respectively on the user's database.changeOwnPassword和changeOwnCustomData操作的权限。
Given a user 在appClient01 in the products database with the following user info:products数据库中为用户appClient01指定以下用户信息:
{
_id : "products.appClient01",
userId : UUID("c5d88855-3f1e-46cb-9c8b-269bef957986"), // Starting in MongoDB 4.0.9
user : "appClient01",
db : "products",
customData : { empID : "12345", badge : "9156" },
roles : [
{
role : "readWrite",
db : "products"
},
{
role : "read",
db : "inventory"
}
],
mechanisms : [
// Starting in MongoDB 4.0
"SCRAM-SHA-1",
"SCRAM-SHA-256"
],
authenticationRestrictions : [ {
clientSource: ["69.89.31.226"],
serverAddress: ["172.16.254.1"]
} ]
}
The following 以下db.updateUser() method completely replaces the user's customData and roles data:db.updateUser()方法完全替换用户的customData和roles数据:
use products db.updateUser( "appClient01", { customData : { employeeId : "0x3039" }, roles : [ { role : "read", db : "assets" } ] } )
The user appClient01 in the products database now has the following user information:products数据库中的用户appClient01现在具有以下用户信息:
{
_id : "products.appClient01",
userId : UUID("c5d88855-3f1e-46cb-9c8b-269bef957986"), // Starting in MongoDB 4.0.9
user : "appClient01",
db : "products",
customData : { employeeId : "0x3039" },
roles : [
{
role : "read",
db : "assets"
}
],
mechanisms : [
// Starting in MongoDB 4.0
"SCRAM-SHA-1",
"SCRAM-SHA-256"
],
authenticationRestrictions : [ {
clientSource: ["69.89.31.226"],
serverAddress: ["172.16.254.1"]
} ]
}
SCRAM-SHA-256 Credentials OnlySCRAM-SHA-256凭据To use SCRAM-SHA-256, the 要使用SCRAM-SHA-256,功能兼容性版本必须设置为featureCompatibilityVersion must be set to 4.0. 4.0。For more information on featureCompatibilityVersion, see View FeatureCompatibilityVersion and 有关setFeatureCompatibilityVersion.featureCompatibilityVersion的更多信息,请参阅查看FeatureCompatibilityVersion和setFeatureCompatibilityVersion。
The following operation updates a user who currently have both 以下操作将当前同时拥有SCRAM-SHA-256 and SCRAM-SHA-1 credentials to have only SCRAM-SHA-256 credentials.SCRAM-SHA-256和SCRAM-SHA-1凭据的用户更新为仅具有SCRAM-SHA-256凭据。
mechanisms, you can only update the mechanisms to a subset of the current SCRAM mechanisms for the user.mechanisms一起指定,则只能将mechanisms更新为用户当前SCRAM机制的子集。mechanisms, you can specify any supported SCRAM mechanism or mechanisms.mechanisms一起指定,则可以指定任何受支持的SCRAM机制。SCRAM-SHA-256, the passwordDigestor must be the default value "server".SCRAM-SHA-256,passwordDigestor必须是默认值“server”。use reporting db.updateUser( "reportUser256", { mechanisms: [ "SCRAM-SHA-256" ] } )