On this page本页内容
db.
createUser
(user, writeConcern)¶Creates a new user for the database on which the method is run. db.createUser()
returns a duplicate user error if the user already exists on the database.
The db.createUser()
method has the following syntax:语法如下所示:
user |
document | The document with authentication and access information about the user to create. |
writeConcern |
document | writeConcern document takes the same fields as the getLastError command. |
The user
document defines the user and has the following form:
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.
The user
document has the following fields:
user |
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. |
authenticationRestrictions | array | Optional. The authentication restrictions the server enforces on the created user. Specifies a list of IP addresses and CIDR ranges from which the user is allowed to connect to the server or from which the server can accept users.
|
mechanisms |
array |
Valid values are:
The default for featureCompatibilityVersion is The default for featureCompatibilityVersion is
|
passwordDigestor |
string |
Available values are:
|
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.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.
The db.createUser()
method wraps the createUser
command.
Starting in version 4.0.9, MongoDB automatically assigns a unique userId
to the user upon creation.
If run on a replica set, db.createUser()
is executed using majority
write concern by default.
Warning
By default, db.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 db.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 db.createUser()
operation creates the accountAdmin01
user 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.
The operation gives accountAdmin01
the following roles:
clusterAdmin
and readAnyDatabase
roles on the admin
databasereadWrite
role on the products
databaseThe following operation creates accountUser
in the products
database and gives the user the readWrite
and dbAdmin
roles.
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.
The following operation creates a user named reportsUser
in the admin
database but does not yet assign roles:
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.
The following operation creates a user named appAdmin
in the admin
database and gives the user readWrite
access to the config
database, which lets the user change certain settings for sharded clusters, such as to the balancer setting.
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.
The following operation creates a user named restricted
in the admin
database. This user may only authenticate if connecting from IP address 192.0.2.0
to IP address 198.51.100.0
.
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.
SCRAM-SHA-256
Credentials Only¶Note
To use SCRAM-SHA-256, the featureCompatibilityVersion
must be set to 4.0
. For more information on featureCompatibilityVersion, see View FeatureCompatibilityVersion and setFeatureCompatibilityVersion
.
The following operation creates a user with only SCRAM-SHA-256
credentials.
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.
If the authenticationMechanisms
parameter is set, the mechanisms
field can only include values specified in the authenticationMechanisms
parameter.