[DOCS-15624] Internal member auth is not listed as a pre-requisite for configuring LDAP authorization on a replica set Created: 12/Sep/22 Updated: 30/Oct/23 Resolved: 12/Jul/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | currentVersion |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Shane Smith | Assignee: | Sarah Simpers |
| Resolution: | Done | Votes: | 0 |
| Labels: | server-docs-bug-bash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 21 weeks, 2 days ago |
| Story Points: | 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...
This requirement was established via https://jira.mongodb.org/browse/SERVER-48516 |