@@ -241,16 +241,15 @@ settings <net-tls-conf-options>` in your
241
241
bindIp: localhost,mongodb0.example.net
242
242
port: 27017
243
243
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:
246
246
247
247
.. code-block:: bash
248
248
249
249
mongod --config <path/to/configuration/file>
250
250
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.
254
253
255
254
.. seealso::
256
255
@@ -363,16 +362,16 @@ For example, consider the following :ref:`configuration file
363
362
bindIp: localhost,mongodb0.example.net
364
363
port: 27017
365
364
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
368
367
its clients:
369
368
370
369
.. code-block:: bash
371
370
372
371
mongod --config <path/to/configuration/file>
373
372
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
376
375
:ref:`mongo-connect-require-client-certificates-tls` for more
377
376
information on connecting with TLS/SSL.
378
377
@@ -390,6 +389,7 @@ information on connecting with TLS/SSL.
390
389
:option:`--tlsCertificateKeyFile <mongos --tlsCertificateKeyFile>`,
391
390
:option:`--tlsCAFile <mongos --tlsCAFile>`.
392
391
392
+ .. _block-revoked-certs-tls:
393
393
394
394
Block Revoked Certificates for Clients
395
395
``````````````````````````````````````
@@ -400,46 +400,36 @@ Block Revoked Certificates for Clients
400
400
MongoDB 4.2). For procedures using the ``net.ssl`` settings, see
401
401
:ref:`configure-ssl`.
402
402
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
405
404
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.
412
408
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:
423
410
424
- .. code-block:: yaml
425
- :emphasize-lines: 6
411
+ .. code-block:: yaml
412
+ :emphasize-lines: 6
426
413
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
433
420
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.
436
423
437
- .. seealso::
424
+ .. seealso::
438
425
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.
440
428
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>`.
443
433
444
434
.. _ssl-mongod-weak-certification:
445
435
@@ -736,16 +726,15 @@ your :binary:`mongod` / :binary:`mongos` instance's
736
726
bindIp: localhost,mongodb0.example.net
737
727
port: 27017
738
728
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:
741
731
742
732
.. code-block:: bash
743
733
744
734
mongod --config <path/to/configuration/file>
745
735
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.
749
738
750
739
.. seealso::
751
740
@@ -849,16 +838,16 @@ For example, consider the following :ref:`configuration file
849
838
bindIp: localhost,mongodb0.example.net
850
839
port: 27017
851
840
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
854
843
its clients:
855
844
856
845
.. code-block:: bash
857
846
858
847
mongod --config <path/to/configuration/file>
859
848
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
862
851
:ref:`mongo-connect-require-client-certificates-tls` for more
863
852
information on connecting with TLS/SSL.
864
853
@@ -876,50 +865,38 @@ information on connecting with TLS/SSL.
876
865
:option:`--sslPEMKeyFile <mongos --sslPEMKeyFile>`, and
877
866
:option:`--sslCAFile <mongos --sslCAFile>`.
878
867
868
+ .. _block-revoked-certs-ssl:
869
+
879
870
Block Revoked Certificates for Clients
880
871
``````````````````````````````````````
881
872
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
891
874
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.
892
878
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:
903
880
904
- .. code-block:: yaml
905
- :emphasize-lines: 6
881
+ .. code-block:: yaml
882
+ :emphasize-lines: 6
906
883
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
913
890
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.
916
893
917
- .. seealso::
894
+ .. seealso::
918
895
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.
920
897
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>`.
923
900
924
901
Validate Only if a Client Presents a Certificate
925
902
````````````````````````````````````````````````
0 commit comments