Skip to content

Copy Edited Document - Tony Ai #2685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Copy Edited Document - Tony Ai #2685

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c6fda56
Copy Edited Document - Tony Ai
t3ai Jul 25, 2016
19a98a8
Copy Edited Document - Tony Ai
t3ai Jul 25, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions source/includes/steps-enable-authentication-in-replica-set.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,15 +44,15 @@ source:
ref: deploy-repset-start-members
pre: |
Running a :program:`mongod` with the ``keyFile`` parameter enforces both
:doc:`/core/security-internal-authentication` and
:doc:`/core/security-internal-authentication`, and
:doc:`/core/authorization`.

Start *each* :program:`mongod` in the replica set using either
a configuration file or the command line.

Use the original replica set name for ``replSetName`` when starting each
member. You cannot change the name of a replica set, and attempting to do
so results in errors.
so will results in errors.
---
stepnum: 5
level: 4
Expand Down
10 changes: 5 additions & 5 deletions source/tutorial/enforce-keyfile-access-control-in-existing-replica-set.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,18 +21,18 @@ Enforcing access control on a :term:`replica set` requires configuring:
- Security between connecting clients and the replica set using
:doc:`User Access Controls</core/authorization>`.

For this tutorial, each member of the replica set uses the same internal
For the purpose of this tutorial, each member of the replica set uses the same internal
authentication mechanism and settings.

Enforcing internal authentication also enforces user access control. To
By enforcing internal authentication, the system also enforces user access control. To
connect to the replica set, clients like the :program:`mongo` shell need to
use a :doc:`user account</core/authorization>`. See
:ref:`security-replSet-auth-access-control`.

Cloud Manager and Ops Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----------------------------

If Cloud Manager or Ops Manager is managing your deployment,
If the deployment is managed by Cloud Manager or Ops Manager,
see: ``Configure Access Control for MongoDB Deployments``
in the :mms-docs:`Cloud Manager manual
</tutorial/edit-host-authentication-credentials>`
Expand All @@ -52,7 +52,7 @@ Keyfile Security
~~~~~~~~~~~~~~~~

Keyfiles are bare-minimum forms of security and are best suited for testing or
development environments. For production environments we recommend using
development environments. For production environments, users are recommended to use
:doc:`x.509 certificates</core/security-x.509>`.

.. _security-replSet-auth-access-control:
Expand Down