[DOCS-9968] Document how to enable authentication in a new replica set deployment Created: 05/Mar/17 Updated: 23/Aug/17 Resolved: 11/Apr/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ivan Grigolon | Assignee: | Kevin Adistambha |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 44 weeks, 1 day ago | ||||
| Description |
|
The security docs regarding "enabling access control for a NEW replica set" has led to some confusion in the community, leading to some people believing there is a mistake or a missed step in creating their new replica set deployment. Although the tutorial enable auth explicitly mentions how to enable internal authentication, users have been searching for how to deploy a replica set with auth enabled. For new MongoDB users, it's difficult to make the connection between auth and internal authentication concepts. Some users believe that the documentation is not highlighting that "a replica set deployment needs internal authentication between members when access control is enabled". Some examples: https://groups.google.com/forum/#!topic/mongodb-user/9xTL6ruKeTQ I believe this part of the documentation could be improved, for example we could add:
|
| Comments |
| Comment by Githook User [ 11/Apr/17 ] |
|
Author: {u'username': u'kevinadi', u'name': u'Kevin Adistambha', u'email': u'kevinadi@gmail.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |