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

Document how to enable authentication in a new replica set deployment

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • true

    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
      https://groups.google.com/forum/#!topic/mongodb-user/Fowgh28ZucA

      I believe this part of the documentation could be improved, for example we could add:

      • A tutorial page on how to deploy a NEW replica set with user authentication
      • A link to the Internal Authentication in the Enable Auth page, with a text of e.g. "To enable auth on a new replica set deployment, please see Internal Authentication"
      • A prominent information box in the Enable Auth documentation that in case of a replica set, internal authentication will need to be enabled.

      Attachments

        Activity

          People

            kevin.adistambha@mongodb.com Kevin Adistambha
            ivan.grigolon@mongodb.com Ivan Grigolon
            Jonathan Dahl Jonathan Dahl
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              5 years, 24 weeks, 6 days ago