@@ -1674,11 +1674,11 @@ Core Options
16741674
16751675 .. include:: /includes/extracts/tls-facts-x509-invalid-certificate.rst
16761676
1677- When using
1678- the :setting:`net.tls.allowInvalidCertificates` setting, MongoDB
1677+ When using the ``net.tls.allowInvalidCertificates`` setting, MongoDB
16791678 logs a warning regarding the use of the invalid certificate.
16801679
1681- .. include:: /includes/extracts/tls-facts-see-more.rst
1680+ For more information about TLS and MongoDB, see
1681+ :ref:`configure-mongod-mongos-for-tls-ssl` and :ref:`inter-process-auth`.
16821682
16831683
16841684.. setting:: net.tls.allowInvalidHostnames
@@ -1687,12 +1687,14 @@ Core Options
16871687
16881688 *Default*: false
16891689
1690- When :setting:`net.tls.allowInvalidHostnames` is ``true``, MongoDB disables the validation of the
1691- hostnames in TLS certificates, allowing :binary:`~bin.mongod` to connect to
1692- MongoDB instances if the hostname their certificates do not match the
1693- specified hostname.
1690+ When ``net.tls.allowInvalidHostnames`` is ``true``, MongoDB disables
1691+ the validation of the hostnames in TLS certificates. This allows
1692+ :binary:`~bin.mongod` or :binary:`~bin.mongos` to connect to other MongoDB
1693+ instances in the cluster, even if the hostname of their certificates does not
1694+ match the specified hostname.
16941695
1695- .. include:: /includes/extracts/tls-facts-see-more.rst
1696+ For more information about TLS and MongoDB, see
1697+ :ref:`configure-mongod-mongos-for-tls-ssl`.
16961698
16971699
16981700.. setting:: net.tls.disabledProtocols
0 commit comments