db.createUser()
Definition
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 theuser already exists on the database.
The db.createUser()
method has the following syntax:
FieldTypeDescriptionuser
documentThe document with authentication and access information about theuser to create.writeConcern
documentOptional. The level of write concern for thecreation operation. The writeConcern
document takes the samefields 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 canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
- {
- user: "<name>",
- pwd: passwordPrompt(), // Or "<cleartext password>"
- customData: { <any information> },
- roles: [
- { role: "<role>", db: "<database>" } | "<role>",
- ...
- ],
- authenticationRestrictions: [
- {
- clientSource: ["<IP>" | "<CIDR range>", ...],
- serverAddress: ["<IP>" | "<CIDR range>", ...]
- },
- ...
- ],
- mechanisms: [ "<SCRAM-SHA-1|SCRAM-SHA-256>", ... ],
- passwordDigestor: "<server|client>"
- }
The user
document has the following fields:
FieldTypeDescriptionuser
stringThe name of the new user.pwd
stringThe user’s password. The pwd
field is notrequired if you run db.createUser()
on the $external
database to create users who have credentials stored externally toMongoDB.
The value can be either:
- the user’s password in cleartext string, or
passwordPrompt()
to prompt for the user’s password.
Tip
Starting in version 4.2 of the mongo
shell, you canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
customData
documentOptional. Any arbitrary information. This field can be used to store any dataan admin wishes to associate with this particular user. For example,this could be the user’s full name or employee id.roles
arrayThe roles granted to the user. Can specify an empty array []
tocreate users without roles.authenticationRestrictions
arrayOptional. The authentication restrictions the server enforces on the createduser. Specifies a list of IP addresses andCIDR ranges from which theuser is allowed to connect to the server or from which the server canaccept users.
New in version 3.6.
mechanisms
arrayOptional. Specify the specific SCRAM mechanism or mechanisms for creatingSCRAM user credentials. If authenticationMechanisms
isspecified, you can only specify a subset of theauthenticationMechanisms
.
Valid values are:
"SCRAM-SHA-1"
- Uses the
SHA-1
hashing function.
- Uses the
"SCRAM-SHA-256"
- Uses the
SHA-256
hashing function. - Requires featureCompatibilityVersion set to
4.0
. - Requires passwordDigestor to be
server
.The default for featureCompatibilityVersion is4.0
is bothSCRAM-SHA-1
andSCRAM-SHA-256
.
- Uses the
The default for featureCompatibilityVersion is 3.6
isSCRAM-SHA-1
.
New in version 4.0.
passwordDigestor
stringOptional. Indicates whether the server or the client digests the password.
Available values are:
"server"
(Default)- The server receives undigested password from the client anddigests the password.
"client"
(Not compatible withSCRAM-SHA-256
)- The client digests the password and passes the digestedpassword to the server.
Changed in version 4.0: The default value is "server"
. In earlier versions, thedefault value is "client"
.
Roles
In the roles
field, you can specify bothbuilt-in roles and user-definedroles.
To specify a role that exists in the same database wheredb.createUser()
runs, you can either specify the role with the name ofthe 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 rolewith a document.
Authentication Restrictions
New in version 3.6.
The authenticationRestrictions
document can contain only thefollowing fields. The server throws an error if theauthenticationRestrictions
document contains an unrecognized field:
Field Name | Value | Description |
---|---|---|
clientSource | Array of IP addresses and/orCIDR ranges | If present, when authenticating a user, the server verifiesthat the client’s IP address is either in the given list orbelongs to a CIDR range in the list. If the client’s IP addressis not present, the server does not authenticate the user. |
serverAddress | Array of IP addresses and/orCIDR ranges | A list of IP addresses or CIDR ranges to which the client canconnect. If present, the server will verify that the client’sconnection was accepted via an IP address in the given list. Ifthe connection was accepted via an unrecognized IP address, theserver does not authenticate the user. |
Important
If a user inherits multiple roles with incompatible authenticationrestrictions, that user becomes unusable.
For example, if a user inherits one role in which theclientSource
field is ["198.51.100.0"]
and another role inwhich the clientSource
field is ["203.0.113.0"]
the server isunable to authenticate the user.
For more information on authentication in MongoDB, seeAuthentication.
The db.createUser()
method wraps the createUser
command.
Behavior
User Id
Starting in version 4.0.9, MongoDB automatically assigns a uniqueuserId
to the user upon creation.
Replica set
If run on a replica set, db.createUser()
is executed using majority
write concern by default.
Encryption
Warning
By default, db.createUser()
sends all specified data to the MongoDBinstance in cleartext, even if using passwordPrompt()
. UseTLS transport encryption to protect communications between clientsand the server, including the password sent by db.createUser()
. Forinstructions on enabling TLS transport encryption, seeConfigure mongod and mongos for TLS/SSL.
MongoDB does not store the password in cleartext. The passwordis only vulnerable in transit between the client and theserver, and only if TLS transport encryption is not enabled.
External Credentials
Users created on the $external
database should have credentialsstored externally to MongoDB, as, for example, with MongoDBEnterprise 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 greaterthan 10k bytes.
local Database
You cannot create users on the local database.
Required Access
- To create a new user in a database, you must have the
createUser
action onthat database resource. - To grant roles to a user, you must have the
grantRole
action on the role’s database.
The userAdmin
anduserAdminAnyDatabase
built-in rolesprovide createUser
andgrantRole
actions on their respective resources.
Examples
The following db.createUser()
operation creates theaccountAdmin01
user on the products
database.
Tip
Starting in version 4.2 of the mongo
shell, you canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
- use products
- db.createUser( { user: "accountAdmin01",
- pwd: passwordPrompt(), // Or "<cleartext password>"
- customData: { employeeId: 12345 },
- roles: [ { role: "clusterAdmin", db: "admin" },
- { role: "readAnyDatabase", db: "admin" },
- "readWrite"] },
- { w: "majority" , wtimeout: 5000 } )
The operation gives accountAdmin01
the following roles:
- the
clusterAdmin
andreadAnyDatabase
roles on theadmin
database - the
readWrite
role on theproducts
database
Create User with Roles
The following operation creates accountUser
in the products
databaseand gives the user the readWrite
and dbAdmin
roles.
Tip
Starting in version 4.2 of the mongo
shell, you canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
- use products
- db.createUser(
- {
- user: "accountUser",
- pwd: passwordPrompt(), // Or "<cleartext password>"
- roles: [ "readWrite", "dbAdmin" ]
- }
- )
Create User without Roles
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 canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
- use admin
- db.createUser(
- {
- user: "reportsUser",
- pwd: passwordPrompt(), // Or "<cleartext password>"
- roles: [ ]
- }
- )
Create Administrative User with Roles
The following operation creates a user named appAdmin
in theadmin
database and gives the user readWrite
access to theconfig
database, which lets the user change certain settings forsharded clusters, such as to the balancer setting.
Tip
Starting in version 4.2 of the mongo
shell, you canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
- use admin
- db.createUser(
- {
- user: "appAdmin",
- pwd: passwordPrompt(), // Or "<cleartext password>"
- roles:
- [
- { role: "readWrite", db: "config" },
- "clusterAdmin"
- ]
- }
- )
Create User with Authentication Restrictions
The following operation creates a user named restricted
in theadmin
database. This user may only authenticate if connecting fromIP address 192.0.2.0
to IP address 198.51.100.0
.
Tip
Starting in version 4.2 of the mongo
shell, you canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
- use admin
- db.createUser(
- {
- user: "restricted",
- pwd: passwordPrompt(), // Or "<cleartext password>"
- roles: [ { role: "readWrite", db: "reporting" } ],
- authenticationRestrictions: [ {
- clientSource: ["192.0.2.0"],
- serverAddress: ["198.51.100.0"]
- } ]
- }
- )
Create User with SCRAM-SHA-256 Credentials Only
Note
To use SCRAM-SHA-256, thefeatureCompatibilityVersion
must be set to 4.0
. For moreinformation on featureCompatibilityVersion, see View FeatureCompatibilityVersion andsetFeatureCompatibilityVersion
.
The following operation creates a user with only SCRAM-SHA-256
credentials.
Tip
Starting in version 4.2 of the mongo
shell, you canuse the passwordPrompt()
method in conjunction withvarious user authentication/management methods/commands to promptfor the password instead of specifying the password directly in themethod/command call. However, you can still specify the passworddirectly as you would with earlier versions of themongo
shell.
- use reporting
- db.createUser(
- {
- user: "reportUser256",
- pwd: passwordPrompt(), // Or "<cleartext password>"
- roles: [ { role: "readWrite", db: "reporting" } ],
- mechanisms: [ "SCRAM-SHA-256" ]
- }
- )
If the authenticationMechanisms
parameter is set, themechanisms
field can only include values specified in theauthenticationMechanisms
parameter.