DOCS-9792 Add authentication steps for replica set > sharded cluster conversion tutorial (#2344)

* WIP

* WIP

* WIP

* more additions

* WIP

* fix indentation

* fix indentation

* fix shard server intro formatting

* try different formatting

* formatting

* edits

* step 4

* formatting

* finalize new formatting

* wording

* wording

* formatting

* WIP

* WIP

* final first draft

* copy fix

* edits

* more edits

* fix broken ref

* add Next Steps section

* formatting for Before You Begin

* add context for initial replica set

* edits

* fix spacing

* wording

* fix code block formatting

* WIP review edits

* WIP review edits

* WIP

* final review edits

* table formatting

* minimalism

* clarifications

* add periods at end of step titles

* more edits

* auth clarifications

* wording

* wording

* more review edits

* fix mongodump command

* first pass at tabs

* Fix formatting

* more edits

* add steps to mongosh command

* more edits

* WIP

* wip

* more edits

* remove extra text

* wip

* more tabs

* formatting

* up to restart secondary as a shard

* final review edits

* ordering

* formatting

* remove extra text

* adjust step 1 to use config files

* fix keyfile yaml file

* fix x509 yaml file

* update step 3 to use config files

* cleanup for steps 1 and 2

* adjust step 5a to use config files

* more config file conversions and general tweaks

* fix quotes for 'number'

* add tip for balancer window

* edit tip title

* fix formatting

* use setting instead of option

* address Linda's comments

* move bindIp warning

* wording

* final edits

* address Linda's feedback

* adjust step styling

* fix indentation

* typos and minor improvements

* fix connection string formatting (at sign)

* add tlsCertificateKeyFile file option to mongosh commands

* single-sourcing

* address review comments

* add tabs for connect to primary step

Author: jeff-allen-mongo

source/includes/fact-shardsvr-required.rst

@@ -0,0 +1,3 @@
+Include additional options as appropriate for your deployment, such as
+:setting:`net.tls.certificateKeyFilePassword` if your TLS certificate-key file is
+encrypted with a password.

source/includes/sharding/convert-repl-set-tutorial/additional-tls-options.rst

@@ -0,0 +1 @@
+Include additional options as appropriate for your deployment.

source/includes/sharding/convert-repl-set-tutorial/include-additional-options.rst

@@ -0,0 +1,3 @@
+The preceding command requires the :ref:`localhost exception
+<localhost-exception>` to perform administrative actions without
+authentication. 

source/includes/sharding/convert-repl-set-tutorial/localhost-exception-preceding.rst

@@ -0,0 +1,6 @@
+If your deployment uses x.509 authentication, specify these
+:binary:`mongosh` options:
+
+- :option:`--tls <mongosh --tls>`
+- :option:`--tlsCAFile <mongosh --tlsCAFile>`
+- :option:`--tlsCertificateKeyFile <mongosh --tlsCertificateKeyFile>`

source/includes/sharding/convert-repl-set-tutorial/mongosh-tls-options.rst

@@ -1,8 +1,8 @@
 .. warning::
 
-   Before binding to a non-localhost (e.g. publicly accessible) 
-   IP address, ensure you have secured your cluster from unauthorized
-   access. For a complete list of security recommendations, see 
-   :doc:`/administration/security-checklist`. At minimum, consider 
-   :ref:`enabling authentication <checklist-auth>` and 
-   :doc:`hardening network infrastructure </core/security-hardening>`.
+   Before you bind your instance to a publicly-accessible IP address,
+   you must secure your cluster from unauthorized access. For a complete
+   list of security recommendations, see
+   :ref:`security-checklist`. At minimum, consider
+   :ref:`enabling authentication <checklist-auth>` and :ref:`hardening
+   network infrastructure <network-config-hardening>`.

source/includes/warning-bind-ip-security-considerations.rst

@@ -1,3 +1,5 @@
+.. _back-up-sharded-cluster-metadata:
+
 ========================
 Back Up Cluster Metadata
 ========================