@@ -244,24 +244,21 @@ The driver checks for your credentials in the following sources in order:
244
244
245
245
The ``X.509`` authentication mechanism uses
246
246
:wikipedia:`TLS <Transport_Layer_Security>` with X.509 certificates to
247
- authenticate your user, identified by the distinguished name (DN) of your
248
- client certificate. For more information on determining the *subject* name from
249
- the X.509 certificate, see the MongoDB manual :manual:`X.509 tutorial
250
- </tutorial/configure-x509-client-authentication/#add-x-509-certificate-subject-as-a-user>`.
247
+ authenticate by retrieving the distinguished name (DN) from the
248
+ client certificate.
251
249
252
250
You can specify this authentication mechanism by setting the following
253
- parameters of your
254
- :manual:`connection string </reference/connection-string/>`:
251
+ parameters of your :manual:`connection string </reference/connection-string/>`:
255
252
256
- - Set the ``authMechanism`` parameter to the value ``MONGODB-X509``
257
- - Set the ``tls`` parameter to the value ``true``
253
+ - Set the ``authMechanism`` parameter to ``MONGODB-X509``
254
+ - Set the ``tls`` parameter to ``true``
258
255
259
256
Pass the location of your client certificate file as the value of
260
257
``tlsCertificateKeyFile`` as a parameter of the connection URI.
261
258
262
259
.. important::
263
- Always **URI encode** the username and certificate file path using the
264
- ``encodeURIComponent`` method to ensure they are correctly parsed.
260
+ Always **URI encode** the certificate file path using the
261
+ ``encodeURIComponent`` method to ensure it is parsed correctly .
265
262
266
263
.. literalinclude:: /code-snippets/authentication/x509.js
267
264
:language: javascript
0 commit comments