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