@@ -15,20 +15,26 @@ content: |
1515
1616 - Each unique MongoDB user must have a unique certificate.
1717
18- - A client x.509 certificate's subject, which contains the
19- Distinguished Name (``DN``), must **differ** from that of a
20- :ref:`x509-member-certificate`.
21-
22- At least one of the Organization (``O``), Organizational Unit
23- (``OU``), or Domain Component (``DC``) attributes in the client
24- certificate must differ from those in the
25- :setting:`net.tls.clusterFile` and
26- :setting:`net.tls.certificateKeyFile` server certificates.
27-
28- If the MongoDB deployment has
29- :parameter:`tlsX509ClusterAuthDNOverride` set (available starting
30- in MongoDB 4.2), the client x.509 certificate's subject must also
31- differ from that value.
18+ - The ``subject`` of a client x.509 certificate, which contains the
19+ Distinguished Name (``DN``), must be **different** than the ``subject``\s
20+ of :ref:`member x.509 certificates <x509-member-certificate>`.
21+
22+ .. important::
23+
24+ If a client x.509 certificate's subject matches the ``O``, ``OU``, and
25+ ``DC`` attributes of the :ref:`x509-member-certificate` (or
26+ :parameter:`tlsX509ClusterAuthDNOverride`, if set) exactly, the client
27+ connection is accepted, full permissions are granted, and a warning
28+ message appears in the log.
29+
30+ Only :ref:`cluster member x509 certificates <x509-member-certificate>`
31+ should use the same ``O``, ``OU``, and ``DC`` attribute combinations.
32+
33+
34+ .. versionadded:: 4.2
35+
36+ If the MongoDB deployment has :parameter:`tlsX509ClusterAuthDNOverride`
37+ set, the client x.509 certificate's subject must not match that value.
3238
3339 .. warning::
3440
@@ -91,11 +97,10 @@ content: |
9197 CN=host2,OU=Dept1,O=MongoDB
9298
9399 - Either the Common Name (``CN``) or one of the Subject Alternative
94- Name (``SAN``) entries must match the hostname of the server, used
95- by the other members of the cluster. Starting in MongoDB 4.2, when
96- performing comparison of SAN, MongoDB supports comparison of DNS
97- names or IP addresses. In previous versions, MongoDB only supports
98- comparisons of DNS names.
100+ Name (``SAN``) entries must match the server hostname for other cluster
101+ members. Starting in MongoDB 4.2, when comparing ``SAN``\s, MongoDB can
102+ compare either DNS names or IP addresses. In previous versions, MongoDB
103+ only compares DNS names.
99104
100105 For example, the certificates for a cluster could have the following
101106 subjects:
0 commit comments