On this page本页内容
createUser¶Creates a new user on the database where you run the command. The createUser command returns a duplicate user error if the user exists. The createUser command uses the following syntax:
Tip
Starting in version 4.2 of the 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. However, you can still specify the password directly as you would with earlier versions of the mongo shell.
createUser has the following fields:
createUser |
string | The name of the new user. |
pwd |
string | The user’s password. The The value can be either:
Tip Starting in version 4.2 of the |
customData |
document | |
roles |
array | The roles granted to the user. Can specify an empty array [] to create users without roles. |
digestPassword |
boolean |
If true, the server receives undigested password from the client and digests the password. If false, the client digests the password and passes the digested password to the server. Not compatible with
|
writeConcern |
document | writeConcern document takes the same fields as the getLastError command. |
authenticationRestrictions |
array |
|
mechanisms |
array |
Valid values are:
The default for featureCompatibilityVersion is The default for featureCompatibilityVersion is
|
digestPassword |
boolean |
If true, the server receives undigested password from the client and digests the password. If false, the client digests the password and passes the digested password to the server. Not compatible with Changed in version 4.0:The default value is |
comment |
any |
A comment can be any valid BSON type (string, integer, object, array, etc).
|
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 createUser runs, you can either specify the role with the name of the role:
Or you can specify the role with a document, as in:
To specify a role that exists in a different database, specify the role with a document.
New in version 3.6.版本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 | |
|---|---|---|
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.
Starting in version 4.0.9, MongoDB automatically assigns a unique userId to the user upon creation.
Warning
By default, createUser sends all specified data to the MongoDB instance in cleartext, even if using passwordPrompt(). Use TLS transport encryption to protect communications between clients and the server, including the password sent by createUser. For instructions on enabling TLS transport encryption, see Configure mongod and mongos for TLS/SSL.
MongoDB does not store the password in cleartext. The password is only vulnerable in transit between the client and the server, and only if TLS transport encryption is not enabled.
Users created on the $external database should have credentials stored externally to MongoDB, as, for example, with MongoDB Enterprise installations that use Kerberos.
Changed in version 3.6.3:To use sessions with $external authentication users (i.e. Kerberos, LDAP, x.509 users), the usernames cannot be greater than 10k bytes.
local Database¶You cannot create users on the local database.
createUser action on that database resource.grantRole action on the role’s database.The userAdmin and userAdminAnyDatabase built-in roles provide createUser and grantRole actions on their respective resources.
The following createUser command creates a user accountAdmin01 on the products database. The command gives accountAdmin01 the clusterAdmin and readAnyDatabase roles on the admin database and the readWrite role on the products database:
Tip
Starting in version 4.2 of the 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. However, you can still specify the password directly as you would with earlier versions of the mongo shell.