[DOCS-1102] How to bootstrap a MongoDB Instance with the correct roles Created: 07/Feb/13 Updated: 03/May/13 Resolved: 03/May/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-2.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark porter | Assignee: | Mark porter |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 41 weeks, 5 days ago | ||||
| Description |
|
Need to document how an end-user should bootstrap their MongoDB infrastructure when running with Kerberos authentication so he/she doesn't lock themselves out of the database so-to-speak. |
| Comments |
| Comment by Mark porter [ 03/May/13 ] |
|
Looking at this latest doc, this ticket can be resolved. |
| Comment by Sam Kleinman (Inactive) [ 28/Feb/13 ] |
|
I'm not sure what constitutes "the correct roles" and what we think best practice is on this. Can you take a look at this and see if you're aware of what makes the most sense? |