@@ -317,17 +317,25 @@ If your application runs on an Azure VM, or otherwise uses the
317
317
support.
318
318
319
319
You can specify Azure IMDS OIDC authentication either by
320
- using a ``MongoCredential`` or as part of the connection string. Select the
321
- :guilabel:`Connection String` or :guilabel:`MongoCredential` tab to
320
+ using a ``MongoCredential`` or as part of the connection string.
321
+
322
+ Select from the :guilabel:`Connection String` or :guilabel:`MongoCredential` tabs to
322
323
see the corresponding syntax.
323
324
324
325
.. tabs::
325
326
326
327
.. tab:: Connection String
327
328
:tabid: mongodb-azure-imds-connection-string
328
329
329
- Replace the ``<percent-encoded audience>`` placeholder with the percent-encoded
330
- value of the ``audience`` server parameter configured on your MongoDB deployment.
330
+ Replace the ``<percent-encoded audience>`` placeholder in the
331
+ following code with the percent-encoded value of the audience server
332
+ parameter configured on your MongoDB deployment.
333
+
334
+ The comma (``,``) character and its encoding (``%2C``) are
335
+ reserved, and using these characters in a value causes the
336
+ driver to interpret commas as delimiters of key-value pairs.
337
+ You must specify values that contain commas in a ``MongoCredential`` instance, as
338
+ demonstrated in the :guilabel:`MongoCredential` tab.
331
339
332
340
.. code-block:: java
333
341
@@ -360,25 +368,33 @@ see the corresponding syntax.
360
368
.. _java-mongodb-oidc-gcp-imds:
361
369
362
370
GCP IMDS
363
- ++++++++++
371
+ ++++++++
364
372
365
373
If your application runs on a GCP VM, or otherwise uses the
366
374
`GCP Instance Metadata Service <https://cloud.google.com/compute/docs/metadata/querying-metadata>`__,
367
375
you can authenticate to MongoDB by using {+driver-short+}'s built-in GCP
368
376
support.
369
377
370
378
You can specify GCP IMDS OIDC authentication either by
371
- using a ``MongoCredential`` or as part of the connection string. Select the
372
- :guilabel:`Connection String` or :guilabel:`MongoCredential` tab to
379
+ using a ``MongoCredential`` or as part of the connection string.
380
+
381
+ Select from the :guilabel:`Connection String` or :guilabel:`MongoCredential` tabs to
373
382
see the corresponding syntax.
374
383
375
384
.. tabs::
376
385
377
386
.. tab:: Connection String
378
387
:tabid: mongodb-gcp-imds-connection-string
379
388
380
- Replace the ``<percent-encoded audience>`` placeholder with the percent-encoded
381
- value of the ``audience`` server parameter configured on your MongoDB deployment.
389
+ Replace the ``<percent-encoded audience>`` placeholder in the
390
+ following code with the percent-encoded value of the audience server
391
+ parameter configured on your MongoDB deployment.
392
+
393
+ The comma (``,``) character and its encoding (``%2C``) are
394
+ reserved, and using these characters in a value causes the
395
+ driver to interpret commas as delimiters of key-value pairs.
396
+ You must specify values that contain commas in a ``MongoCredential`` instance, as
397
+ demonstrated in the :guilabel:`MongoCredential` tab.
382
398
383
399
.. code-block:: java
384
400
0 commit comments