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

Incorrect config attribute in step 9 of enforce-keyfile-access-control-in-existing-replica-set-without-downtime

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • manual, Server
    • None

    Description

      Description

      In our tutorial to enforce key access control in replica sets without downtime, the last paragraph of step nine, reads:

      At the end of this step, all secondaries and arbiters should be up and running with internal authentication configured, but without security.keyFile. Clients can only connect to these mongod instances by using the configured client authentication mechanism.

      I believe it was meant to say "but without security.transitionToAuth" because "security.keyFile" is meant to stay there after the procedure is finished. Otherwise, authentication won't work (at least from the steps given up to that point and after in the tutorial).

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Activity

          People

            isabella.siu@mongodb.com Isabella Siu (Inactive)
            francisco.alanis@mongodb.com Francisco Alanis
            Isabella Siu Isabella Siu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              3 years, 45 weeks ago