@@ -205,24 +205,21 @@ The driver checks for your credentials in the following sources in order:
205
205
206
206
The ``X.509`` authentication mechanism uses
207
207
:wikipedia:`TLS <Transport_Layer_Security>` with X.509 certificates to
208
- authenticate your user, identified by the distinguished name (DN) of your
209
- client certificate. For more information on determining the *subject* name from
210
- the X.509 certificate, see the MongoDB manual :manual:`X.509 tutorial
211
- </tutorial/configure-x509-client-authentication/#add-x-509-certificate-subject-as-a-user>`.
208
+ authenticate by retrieving the distinguished name (DN) from the
209
+ client certificate.
212
210
213
211
You can specify this authentication mechanism by setting the following
214
- parameters of your
215
- :manual:`connection string </reference/connection-string/>`:
212
+ parameters of your :manual:`connection string </reference/connection-string/>`:
216
213
217
- - Set the ``authMechanism`` parameter to the value ``MONGODB-X509``
218
- - Set the ``tls`` parameter to the value ``true``
214
+ - Set the ``authMechanism`` parameter to ``MONGODB-X509``
215
+ - Set the ``tls`` parameter to ``true``
219
216
220
217
Pass the location of your client certificate file as the value of
221
218
``tlsCertificateKeyFile`` as a parameter of the connection URI.
222
219
223
220
.. important::
224
- Always **URI encode** the username and certificate file path using the
225
- ``encodeURIComponent`` method to ensure they are correctly parsed.
221
+ Always **URI encode** the certificate file path using the
222
+ ``encodeURIComponent`` method to ensure it is parsed correctly .
226
223
227
224
.. literalinclude:: /code-snippets/authentication/x509.js
228
225
:language: javascript
0 commit comments