Ops Manager enables you to configure the Authentication Mechanisms that all clients, including the Ops Manager Agents, use to connect to your MongoDB deployments. You can enable multiple authentication mechanisms for each of your projects, but you must choose only one mechanism for the Agents.
MongoDB users can use usernames and passwords to authenticate themselves against a MongoDB database.
Default authentication mechanism
MongoDB 4.0 and later
Salted Challenge Response Authentication Mechanism (SCRAM) using the SHA-1 and SHA-256 hashing algorithms (
MongoDB 3.4 to 3.6
Salted Challenge Response Authentication Mechanism (SCRAM) using the SHA-1 hashing algorithm (
SCRAM-SHA-256 verify supplied user credentials
using the user's name, password and authentication database. The
authentication database is the database where the user was created.
This tutorial describes how to enable Username and Password authentication for your Ops Manager MongoDB deployment.
The MongoDB Community version supports Username and Password authentication and x.509 authentication.
This procedure describes how to configure and enable username and password authentication when using Automation. If Ops Manager does not manage your MongoDB Agents, you must manually configure them to use Usernames and Passwords. To learn how to configure authentication, see Configure MongoDB Agent for Authentication.
If you configure the Ops Manager application to authenticate using SCRAM-SHA-256, you cannot deploy pre-4.0 MongoDB clusters.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
If it is not already displayed, click Deployment in the sidebar.
Click the Security tab.
Click the Settings tab.
Perform one of the following actions:
If this is your first time configuring TLS, authentication, or authorization settings for this project, click Get Started.
If you have already configured TLS authentication, or authorization settings for this project, click Edit.
TLS is not required for use with Username/Password (MONGODB-CR/SCRAM-SHA-1) or Username/Password (SCRAM-SHA-256) authentication.
MongoDB Deployment Transport Layer Security (TLS)
Toggle this slider to ON.
TLS CA File Path
The TLS Certificate Authority file is a
Type the file path to the TLS Certificate Authority file on every host running a MongoDB process:
This enables the
Click Validate to test that each host in your deployment has a TLS Certificate Authority at the paths you specified.
Client Certificate Mode
Select if client applications or MongoDB Agents must present a TLS certificate when connecting to a TLS-enabled MongoDB deployments. Each MongoDB deployment checks for certificates from these client hosts when they try to connect. If you choose to require the client TLS certificates, make sure they are valid.
Accepted values are:
Configure Username/Password (MONGODB-CR/SCRAM-SHA-1) or Username/Password (SCRAM-SHA-256) for the Agent.
You can enable more than one authentication mechanism for your MongoDB deployment, but the Ops Manager Agents can only use one authentication mechanism.
In the MongoDB Agent Connections to Deployment section, select Username/Password (MONGODB-CR/SCRAM-SHA-1) and/or Username/Password (SCRAM-SHA-256).
Ops Manager automatically generates the Agents' usernames and passwords.
Ops Manager creates users for the agents with the required user roles in the admin database for each existing deployment in Ops Manager. When you add a new deployment, Ops Manager creates the required users in the new deployment.