Skip to content

Commit 9bd4533

Browse files
DOCSP-37138 remove OCSP info from TLS tutorial (#6513) (#6532)
* DOCSP-37138 remove OSCP info from TLS tutorial * update ssl section * cleanup * add refs * add missing word * standardization * present tense * typos * typo
1 parent ad3bafb commit 9bd4533

File tree

2 files changed

+63
-83
lines changed

2 files changed

+63
-83
lines changed
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
To prevent clients with revoked certificates from connecting to the
2+
:binary:`~bin.mongod` or :binary:`~bin.mongos` instance, you can use a
3+
Certificate Revocation List (CRL).

source/tutorial/configure-ssl.txt

Lines changed: 60 additions & 83 deletions
Original file line numberDiff line numberDiff line change
@@ -241,16 +241,15 @@ settings <net-tls-conf-options>` in your
241241
bindIp: localhost,mongodb0.example.net
242242
port: 27017
243243

244-
A :binary:`~bin.mongod` instance that uses the above configuration
245-
can only use TLS/SSL connections:
244+
A :binary:`~bin.mongod` instance that uses the above configuration can
245+
only accept TLS/SSL connections:
246246

247247
.. code-block:: bash
248248

249249
mongod --config <path/to/configuration/file>
250250

251-
That is, clients must specify TLS/SSL connections. See
252-
:ref:`tls-client-connection-only` for more information on
253-
connecting with TLS/SSL.
251+
See :ref:`tls-client-connection-only` for more information on connecting
252+
with TLS/SSL.
254253

255254
.. seealso::
256255

@@ -363,16 +362,16 @@ For example, consider the following :ref:`configuration file
363362
bindIp: localhost,mongodb0.example.net
364363
port: 27017
365364

366-
A :binary:`~bin.mongod` instance that uses the above configuration
367-
can only use TLS/SSL connections and requires valid certificate from
365+
A :binary:`~bin.mongod` instance that uses the above configuration can
366+
only accept TLS/SSL connections and requires a valid certificate from
368367
its clients:
369368

370369
.. code-block:: bash
371370

372371
mongod --config <path/to/configuration/file>
373372

374-
That is, clients must specify TLS/SSL connections and presents its
375-
certificate key file to the instance. See
373+
Clients must specify TLS/SSL connections and present their certificate
374+
key file to the instance. See
376375
:ref:`mongo-connect-require-client-certificates-tls` for more
377376
information on connecting with TLS/SSL.
378377

@@ -390,6 +389,7 @@ information on connecting with TLS/SSL.
390389
:option:`--tlsCertificateKeyFile <mongos --tlsCertificateKeyFile>`,
391390
:option:`--tlsCAFile <mongos --tlsCAFile>`.
392391

392+
.. _block-revoked-certs-tls:
393393

394394
Block Revoked Certificates for Clients
395395
``````````````````````````````````````
@@ -400,46 +400,36 @@ Block Revoked Certificates for Clients
400400
MongoDB 4.2). For procedures using the ``net.ssl`` settings, see
401401
:ref:`configure-ssl`.
402402

403-
To prevent clients with revoked certificates from connecting to the
404-
:binary:`~bin.mongod` or :binary:`~bin.mongos` instance, you can use:
403+
.. include:: /includes/security/block-revoked-certificates-intro.rst
405404

406-
- Online Certificate Status Protocol (OCSP)
407-
Starting in version 4.4, to check for certificate revocation,
408-
MongoDB :parameter:`enables <ocspEnabled>` the use of OCSP
409-
(Online Certificate Status Protocol) by default as an alternative
410-
to specifying a CRL file or using the :setting:`system SSL
411-
certificate store <net.tls.certificateSelector>`.
405+
To specify a :abbr:`CRL (Certificate Revocation List)` file, include
406+
:setting:`net.tls.CRLFile` set to a file that contains revoked
407+
certificates.
412408

413-
In versions 4.0 and 4.2, the use of OCSP is available only
414-
through the use of :setting:`system certificate store
415-
<net.tls.certificateSelector>` on Windows or macOS.
416-
417-
- Certificate Revocation List (CRL)
418-
To specify a CRL file, include
419-
:setting:`net.tls.CRLFile` set to a file that contains revoked
420-
certificates.
421-
422-
For example:
409+
For example:
423410

424-
.. code-block:: yaml
425-
:emphasize-lines: 6
411+
.. code-block:: yaml
412+
:emphasize-lines: 6
426413

427-
net:
428-
tls:
429-
mode: requireTLS
430-
certificateKeyFile: /etc/ssl/mongodb.pem
431-
CAFile: /etc/ssl/caToValidateClientCertificates.pem
432-
CRLFile: /etc/ssl/revokedCertificates.pem
414+
net:
415+
tls:
416+
mode: requireTLS
417+
certificateKeyFile: /etc/ssl/mongodb.pem
418+
CAFile: /etc/ssl/caToValidateClientCertificates.pem
419+
CRLFile: /etc/ssl/revokedCertificates.pem
433420

434-
Clients that present certificates that are listed in the
435-
:file:`/etc/ssl/revokedCertificates.pem` will not be able to connect.
421+
Clients that present certificates that are listed in the
422+
:file:`/etc/ssl/revokedCertificates.pem` file are not able to connect.
436423

437-
.. seealso::
424+
.. seealso::
438425

439-
You can also configure the revoked certificate list using the command-line option.
426+
You can also configure the revoked certificate list using the
427+
command-line option.
440428

441-
- For :binary:`~bin.mongod`, see :option:`--tlsCRLFile <mongod --tlsCRLFile>`.
442-
- For :binary:`~bin.mongos`, see :option:`--tlsCRLFile <mongos --tlsCRLFile>`.
429+
- For :binary:`~bin.mongod`, see :option:`--tlsCRLFile <mongod
430+
--tlsCRLFile>`.
431+
- For :binary:`~bin.mongos`, see :option:`--tlsCRLFile <mongos
432+
--tlsCRLFile>`.
443433

444434
.. _ssl-mongod-weak-certification:
445435

@@ -736,16 +726,15 @@ your :binary:`mongod` / :binary:`mongos` instance's
736726
bindIp: localhost,mongodb0.example.net
737727
port: 27017
738728

739-
A :binary:`~bin.mongod` instance that uses the above configuration
740-
can only use TLS/SSL connections:
729+
A :binary:`~bin.mongod` instance that uses the above configuration can
730+
only accept TLS/SSL connections:
741731

742732
.. code-block:: bash
743733

744734
mongod --config <path/to/configuration/file>
745735

746-
That is, clients must specify TLS/SSL connections. See
747-
:ref:`tls-client-connection-only` for more information on
748-
connecting with TLS/SSL.
736+
See :ref:`tls-client-connection-only` for more information on connecting
737+
with TLS/SSL.
749738

750739
.. seealso::
751740

@@ -849,16 +838,16 @@ For example, consider the following :ref:`configuration file
849838
bindIp: localhost,mongodb0.example.net
850839
port: 27017
851840

852-
A :binary:`~bin.mongod` instance that uses the above configuration
853-
can only use TLS/SSL connections and requires valid certificate from
841+
A :binary:`~bin.mongod` instance that uses the above configuration can
842+
only accept TLS/SSL connections and requires a valid certificate from
854843
its clients:
855844

856845
.. code-block:: bash
857846

858847
mongod --config <path/to/configuration/file>
859848

860-
That is, clients must specify TLS/SSL connections and present their
861-
certificate key file to the instance. See
849+
Clients must specify TLS/SSL connections and present their certificate
850+
key file to the instance. See
862851
:ref:`mongo-connect-require-client-certificates-tls` for more
863852
information on connecting with TLS/SSL.
864853

@@ -876,50 +865,38 @@ information on connecting with TLS/SSL.
876865
:option:`--sslPEMKeyFile <mongos --sslPEMKeyFile>`, and
877866
:option:`--sslCAFile <mongos --sslCAFile>`.
878867

868+
.. _block-revoked-certs-ssl:
869+
879870
Block Revoked Certificates for Clients
880871
``````````````````````````````````````
881872

882-
To prevent clients with revoked certificates from connecting to the
883-
:binary:`~bin.mongod` or :binary:`~bin.mongos` instance, you can use:
884-
885-
- Online Certificate Status Protocol (OCSP)
886-
Starting in version 4.4, to check for certificate revocation,
887-
MongoDB :parameter:`enables <ocspEnabled>` the use of OCSP
888-
(Online Certificate Status Protocol) by default as an alternative
889-
to specifying a CRL file or using the :setting:`system SSL
890-
certificate store <net.ssl.certificateSelector>`.
873+
.. include:: /includes/security/block-revoked-certificates-intro.rst
891874

875+
To specify a :abbr:`CRL (Certificate Revocation List)` file, include
876+
:setting:`net.ssl.CRLFile` set to a file that contains revoked
877+
certificates.
892878

893-
In versions 4.0 and 4.2, the use of OCSP is available only
894-
through the use of :setting:`system certificate store
895-
<net.ssl.certificateSelector>` on Windows or macOS.
896-
897-
- Certificate Revocation List (CRL)
898-
To specify a CRL file, include
899-
:setting:`net.ssl.CRLFile` set to a file that contains revoked
900-
certificates.
901-
902-
For example:
879+
For example:
903880

904-
.. code-block:: yaml
905-
:emphasize-lines: 6
881+
.. code-block:: yaml
882+
:emphasize-lines: 6
906883

907-
net:
908-
ssl:
909-
mode: requireSSL
910-
PEMKeyFile: /etc/ssl/mongodb.pem
911-
CAFile: /etc/ssl/caToValidateClientCertificates.pem
912-
CRLFile: /etc/ssl/revokedCertificates.pem
884+
net:
885+
ssl:
886+
mode: requireSSL
887+
PEMKeyFile: /etc/ssl/mongodb.pem
888+
CAFile: /etc/ssl/caToValidateClientCertificates.pem
889+
CRLFile: /etc/ssl/revokedCertificates.pem
913890

914-
Clients that present certificates that are listed in the
915-
:file:`/etc/ssl/revokedCertificates.pem` will not be able to connect.
891+
Clients that present certificates that are listed in the
892+
:file:`/etc/ssl/revokedCertificates.pem` file are not able to connect.
916893

917-
.. seealso::
894+
.. seealso::
918895

919-
You can also configure the revoked certificate list using the command-line option.
896+
You can also configure the revoked certificate list using the command-line option.
920897

921-
- For :binary:`~bin.mongod`, see :option:`--sslCRLFile <mongod --sslCRLFile>`.
922-
- For :binary:`~bin.mongos`, see :option:`--sslCRLFile <mongos --sslCRLFile>`.
898+
- For :binary:`~bin.mongod`, see :option:`--sslCRLFile <mongod --sslCRLFile>`.
899+
- For :binary:`~bin.mongos`, see :option:`--sslCRLFile <mongos --sslCRLFile>`.
923900

924901
Validate Only if a Client Presents a Certificate
925902
````````````````````````````````````````````````

0 commit comments

Comments
 (0)