Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15624

Internal member auth is not listed as a pre-requisite for configuring LDAP authorization on a replica set

    XMLWordPrintableJSON

Details

    • 2

    Description

      The documentation articles on configuring LDAP authentication/authorization should list configuring internal member authentication as a pre-requisite step for replica set/sharded cluster.

      https://www.mongodb.com/docs/v6.0/tutorial/authenticate-nativeldap-activedirectory/

      If a MongoDB enterprise customer follows the above instructions to configure LDAP authentication with authorization on version 4.4 or later, and does not already have internal authentication (i.e. keyFile or x.509) setup for their replica set, then mongod will fail to start with the below error.

      systemd[1]: Starting MongoDB Database Server...
      mongod[17886]: BadValue: security.keyFile is required when authorization is enabled with replica sets
      mongod[17886]: try '/usr/bin/mongod --help' for more information
      systemd[1]: mongod.service: control process exited, code=exited status=2
      systemd[1]: Failed to start MongoDB Database Server.

       

      This requirement was established via 

      https://jira.mongodb.org/browse/SERVER-48516

      Attachments

        Activity

          People

            sarah.simpers@mongodb.com Sarah Simpers
            shane.smith@mongodb.com Shane Smith
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              1 year, 21 weeks, 2 days ago