@@ -201,9 +201,8 @@ On Windows and macOS,
201201 mongosh --tls --host hostname.example.com --tlsCertificateSelector subject="myclient.example.net"
202202
203203 Although still available, :mongosh:`mongosh </>`
204- :option:`--ssl <mongosh --ssl>`, :option:`--sslCAFile <mongo
205- --sslCAFile>`, :option:`--sslPEMKeyFile <mongosh --sslPEMKeyFile>`,
206- :option:`--sslCertificateSelector <mongosh --sslCertificateSelector>`
204+ ``--ssl``, ``--sslCAFile``, ``--sslPEMKeyFile``, and
205+ ``--sslCertificateSelector`` options
207206 are :ref:`deprecated as of MongoDB 4.2 <4.2-tls>`.
208207
209208Avoid Use of ``--tlsAllowInvalidCertificates`` Option
@@ -243,31 +242,31 @@ Avoid Use of ``--tlsAllowInvalidCertificates`` Option
243242 * - SSL Option (Deprecated in 4.2)
244243 - Notes
245244
246- * - :option:` --ssl <mongosh --ssl> `
245+ * - `` --ssl` `
247246 - Enables TLS/SSL connection.
248247
249- * - :option:` --sslPEMKeyFile <mongosh --sslPEMKeyFile> `
248+ * - `` --sslPEMKeyFile` `
250249
251250 - Specifies the :file:`.pem` file that contains
252251 :mongosh:`mongosh </>`'s certificate and key to present to
253252 the :binary:`~bin.mongod` or :binary:`~bin.mongos` instance.
254253
255- * - :option:` --sslPEMKeyPassword <mongosh --sslPEMKeyPassword> `
254+ * - `` --sslPEMKeyPassword` `
256255
257256 - If :mongosh:`mongosh </>`'s certificate key file is encrypted.
258257
259- * - :option:` --sslCAFile <mongosh --sslCAFile> `
258+ * - `` --sslCAFile` `
260259
261260 - Specifies the Certificate Authority (CA) :file:`.pem` file for
262261 verification of the certificate presented by the
263262 :binary:`~bin.mongod` or the :binary:`~bin.mongos` instance.
264263
265- * - :option:` --sslCertificateSelector <mongosh --sslCertificateSelector> `
264+ * - `` --sslCertificateSelector` `
266265
267266 - If running on Windows or macOS, use a certificate from the
268267 system certificate store. (*New in version 4.0*)
269268
270- For a complete list of :mongosh:`mongosh </>`'s ``ssl``
269+ For a complete list of ``ssl``
271270options, see :ref:`SSL Options <mongo-shell-ssl>`.
272271
273272For TLS/SSL connections, :mongosh:`mongosh </>` validates the
@@ -303,7 +302,7 @@ To connect to a :binary:`~bin.mongod` or :binary:`~bin.mongos` instance
303302that requires :ref:`encrypted communication <ssl-mongod-ssl-cert-key>`,
304303start :mongosh:`mongosh </>` with:
305304
306- - :option:` --ssl <mongosh --ssl> `
305+ - `` --ssl` `
307306
308307- :option:`--host <mongosh --host>` and :option:`--sslCAFile <mongo
309308 --sslCAFile>` to validate the server certificate.
@@ -341,12 +340,12 @@ To connect to a :binary:`~bin.mongod` or :binary:`~bin.mongos` that
341340requires :ref:`CA-signed client certificates
342341<ssl-mongod-ca-signed-ssl-cert-key>`, start :mongosh:`mongosh </>` with:
343342
344- - :option:` --ssl <mongosh --ssl> `
343+ - `` --ssl` `
345344
346345- :option:`--host <mongosh --host>` and the :option:`--sslCAFile <mongo
347346 --sslCAFile>` to validate the server certificate,
348347
349- - :option:` --sslPEMKeyFile <mongosh --sslPEMKeyFile> ` option to specify
348+ - `` --sslPEMKeyFile` ` option to specify
350349 the client certificate to present to the server.
351350
352351For example, consider a :binary:`~bin.mongod` instance running on
@@ -367,9 +366,9 @@ On Windows and macOS,
367366 You can also use the :option:`--sslCertificateSelector <mongo
368367 --sslCertificateSelector>` option to specify the client certificate
369368 from the system certificate store instead of using
370- :option:` --sslPEMKeyFile <mongosh --sslPEMKeyFile> `. If the CA file
369+ `` --sslPEMKeyFile` `. If the CA file
371370 is also in the system certificate store, you can omit the
372- :option:` --sslCAFile <mongosh --sslCAFile> ` option as well. For
371+ `` --sslCAFile` ` option as well. For
373372 example, to use a certificate with the ``CN`` (Common Name) of
374373 ``myclient.example.net`` and the CA file from the system certificate
375374 store on macOS, start :mongosh:`mongosh </>` with the following
0 commit comments