Enable Kerberos Authentication for your Ops Manager Group¶
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 groups, but you must choose only one mechanism for the Agents.
MongoDB Enterprise supports authentication using a Kerberos service. Kerberos is an industry standard authentication protocol for large client/server systems.
Setting up and configuring a Kerberos deployment is beyond the scope of this document. This tutorial assumes you have configured a Kerberos principal for each Agent and you have a valid keytab file for each Agent.
To authenticate MongoDB with Kerberos, you must:
- Have a properly configured Kerberos deployment,
- Configure Kerberos service principals for MongoDB, and
- Add the Kerberos user principals for the Agents.
The Kerberos Authentication section of the MongoDB Manual provides more detail about using MongoDB with Kerberos.
Kerberos (GSSAPI) is only available on MongoDB Enterprise builds. If
you have existing deployments running on a MongoDB Community
build, you must upgrade them to MongoDB Enterprise before you can enable
Kerberos (GSSAPI) for your Ops Manager group.
This tutorial describes how to enable Kerberos for one of your Ops Manager groups and how to configure your Ops Manager Agents to connect to your Kerberos-enabled deployment.
If Ops Manager is not managing any MongoDB deployment, you can reset Authentication and SSL settings for your group.
To remove all authentication and security settings as well as the users and roles you created using Ops Manager, click Clear Settings in the Authentication & SSL Settings dialog box .
See Clear Security Settings for more information.
To unmanage MongoDB deployments, see Remove a Process from Management or Monitoring.
These procedures describe how to configure and enable Kerberos authentication when using Automation. If Ops Manager does not manage your Monitoring or Backup agents, you must manually configure them to authenticate using Kerberos.
Configure an Existing Linux Deployment for Kerberos-based Authentication¶
If you use Ops Manager to manage existing deployments on Linux in your group, all MongoDB deployments in the group must be configured for Kerberos authentication before you can enable Kerberos authentication for your group.
Click Deployment, then click the Processes tab, and then the Topology view.¶
On the line listing the process, click Modify.¶
Expand the Advanced Options area.¶
kerberosKeytab Startup option to point to the keytab file and click Apply.¶
kerberosKeytab is not already set, use the Add Option
button to add a new startup option, and select
from the drop-down menu. Input the path to the keytab file
as the value, and then click Apply.
When you have configured the Kerberos options for each deployment, you can proceed to enable Kerberos for your Ops Manager group.
Enable Kerberos for your Ops Manager Group¶
Configure Kerberos (GSSAPI) for the Agents.¶
You can enable more than one authentication mechanism for your MongoDB deployment, but the Ops Manager Agents can only use one authentication mechanism. Select Kerberos (GSSAPI) to connect to your MongoDB deployment.
Select Kerberos (GSSAPI) from the Agent Auth Mechanism drop-down menu.
Enter Agent Credentials for the appropriate operating system:
Only configure the Agents you installed. For example, if you did not install the Backup Agent, do not configure the Backup agent.
If using Linux, configure:
Setting Value <Agent> Kerberos Principal The Kerberos Principal. <Agent> Keytab Path The path for the Agent’s Keytab. <Agent> LDAP Group DN
Enter the Distinguished Name for the Agent’s LDAP Group.
The LDAP Group DN is then created as a role in MongoDB to grant the Agent the appropriate privileges.
You only need to provide the Agent’s LDAP Group DN if you use LDAP Authorization.
If using Windows, configure:
Setting Value <Agent> Username The Active Directory user name. <Agent> Password The Active Directory password. Domain The NetBIOS name of a domain in Active Directory Domain Services. Must be in all capital letters.
Click Review & Deploy to review your changes.¶
Review and approve your changes.¶
Ops Manager displays your proposed changes.
- If you are satisfied, click Confirm & Deploy.
- Otherwise, click Cancel and you can make additional changes.