Kerberos tickets can authenticate users for a limited time. You must configure the Kerberos Key Distribution Center (KDC) to issue tickets that are valid for four hours or longer. The MongoDB Agent periodically renews the ticket. The KDC service provides session tickets and temporary session keys to users and hosts.
The MongoDB Agent interacts with the MongoDB databases in your deployment as a MongoDB user would. As a result, you must configure your MongoDB deployment and the MongoDB Agent to support authentication.
You can specify the deployment's authentication mechanisms when adding the deployment, or you can edit the settings for an existing deployment. At minimum, the deployment must enable the authentication mechanism you want the MongoDB Agent to use. The MongoDB Agent can use any supported authentication mechanism.
For the purposes of this tutorial, you must ensure the following:
Your deployment supports Kerberos authentication and
MongoDB Agent uses Kerberos authentication.
To learn how to enable Kerberos authentication, see Enable Kerberos Authentication for your Cloud Manager Project.
Two Kerberos-related files must be installed on any host running Monitoring or Backup:
Create or configure the krb5.conf Kerberos configuration file.PlatformDefault PathNotesLinux
%WINDIR%\krb5.iniThis is the default path for non-Active Directory-based Kerberos implementations. Refer to the documentation for your Kerberos implemention for your version of Windows to find out where the Kerberos configuration file is stored.
On Linux systems: ensure kinit binary is located at
kinitobtains or renews a Kerberos ticket-granting ticket, which authenticates the Agent using Kerberos.
An UPN is formatted in two parts so the service can be uniquely identified across the Kerberos realm:
The name of one service a host is providing to the Kerberos realm, such as
A set of managed hosts and services that share the same Kerberos database.
By Kerberos naming convention, the
In a Kerberos realm set as
EXAMPLE.COM, the MongoDB Agent
would set its UPN to:
Generate a keytab
*.keytab) for the MongoDB Agent UPN and copy it to the
host that runs the MongoDB Agent. Ensure that the operating system
user that runs the MongoDB Agent is the same operating system user
that owns the