- Security >
- Authentication >
- SCRAM >
- Use SCRAM to Authenticate Clients
Use SCRAM to Authenticate Clients¶
On this page
The following procedure sets up SCRAM for client authentication on a
standalone mongod
instance.
To use SCRAM authentication for replica sets or sharded clusters, see Deploy Replica Set With Keyfile Authentication.
Procedure¶
Start MongoDB without access control¶
Start a standalone mongod
instance without access
control.
Open a terminal and run the following command as the mongod
user:
The mongod
instance in this tutorial uses
port 27017
and the /var/lib/mongodb
data directory.
The tutorial assumes that the /var/lib/mongodb
directory exists
and is the default dbPath
. You may specify a
different data directory or port as needed.
Tip
When mongod
starts, it creates some system files in the
/var/lib/mongodb
directory. To ensure the system files have
the correct ownership, follow this tutorial as the mongod
user. If you start mongod
as the root
user you will
have to update file ownership later.
Connect to the instance¶
Open a new terminal and connect to the database deployment with
mongosh
:
If you are connecting to a different deployment, specify additional
command line options, such as --host
, as
needed to connect.
Create the user administrator¶
Important
Localhost Exception
You can create the user administrator either before or after
enabling access control. If you enable access control before
creating any user, MongoDB provides a localhost exception which allows you to create a user
administrator in the admin
database. Once created, you must
authenticate as the user administrator to create additional users.
Using mongosh
:
- switch to the
admin
database - add the
myUserAdmin
user with theuserAdminAnyDatabase
andreadWriteAnyDatabase
roles”:
Tip
The passwordPrompt()
method prompts you to enter the
password. You can also specify your password directly as a string. We
recommend to use the passwordPrompt()
method to avoid the
password being visible on your screen and potentially leaking the
password to your shell history.
The userAdminAnyDatabase
role allows this user to:
- create users
- grant or revoke roles from users
- create or modify customs roles
You can assign your user additional built-in roles or user-defined roles as needed.
The database where you create the user, in this example admin
,
is the user’s authentication database. Although the user needs to
authenticate to this database, the user can have roles in other
databases. The user’s authentication database doesn’t limit the
user’s privileges.
Re-start the MongoDB instance with access control¶
Shut down the mongod
instance. Using
mongosh
, issue the following command:
Exit mongosh
.
Start the mongod
with access control enabled.
If you start the
mongod
from the command line, add the--auth
command line option:If you start the
mongod
using a configuration file, add thesecurity.authorization
configuration file setting:
Clients that connect to this instance must now authenticate themselves and can only perform actions as determined by their assigned roles.
Important
Localhost Exception
You can create users either before or after enabling access
control. If you enable access control before creating any user,
MongoDB provides a localhost exception which allows you to create a user
administrator in the admin
database. Once created, you must
authenticate as the user administrator to create additional users.
Connect and authenticate as the user administrator¶
Using mongosh
, you can:
- Authenticate during Connection
- Authenticate after Connection
Start mongosh
with the -u
<username>
, -p
, and the
--authenticationDatabase <database>
command line options:
Enter your password when prompted.
Using mongosh
, connect to your database
deployment:
In mongosh
, switch to the
authentication database (in this case, admin
), and
use the db.auth(<username>, <pwd>)
method to authenticate:
Tip
The passwordPrompt()
method prompts you to enter the
password. You can also specify your password directly as a string. We
recommend to use the passwordPrompt()
method to avoid the
password being visible on your screen and potentially leaking the
password to your shell history.
Enter the password when prompted.
Next Steps¶
To use SCRAM authentication for replica sets or sharded clusters, see Deploy Replica Set With Keyfile Authentication.