Skip to content

Commit

Permalink
Changelog; slightly change wording
Browse files Browse the repository at this point in the history
  • Loading branch information
comandeo-mongo committed Apr 19, 2024
1 parent 58f048f commit 76f2f65
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions source/auth/auth.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ If the handshake response includes a `saslSupportedMechs` field, then drivers MU
select a default mechanism as described later. If the command succeeds and the response does not include a
`saslSupportedMechs` field, then drivers MUST use the legacy default mechanism rules for servers older than 4.0.

Drivers MUST NOT validate whether content of the `saslSupportedMechs` attribute of the initial handshake reply. Drivers
Drivers MUST NOT validate the contents of the `saslSupportedMechs` attribute of the initial handshake reply. Drivers
MUST NOT raise an error if the `saslSupportedMechs` attribute of the reply includes an unknown mechanism.

### Single-credential drivers
Expand Down Expand Up @@ -2053,7 +2053,7 @@ to EC2 instance metadata in ECS, for security reasons, Amazon states it's best p

## Changelog

- 2024-04-??: Clarify that driver should not validate `saslSupportedMechs` content.
- 2024-04-19: Clarify that driver should not validate `saslSupportedMechs` content.

- 2024-04-03: Added GCP built-in OIDC provider integration.

Expand Down
4 changes: 2 additions & 2 deletions source/auth/auth.rst
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ to select a default mechanism as described later. If the command succeeds and
the response does not include a ``saslSupportedMechs`` field, then drivers MUST
use the legacy default mechanism rules for servers older than 4.0.

Drivers MUST NOT validate whether content of the ``saslSupportedMechs``
Drivers MUST NOT validate the contents of the ``saslSupportedMechs``
attribute of the initial handshake reply. Drivers MUST NOT raise an error if
the ``saslSupportedMechs`` attribute of the reply includes an unknown mechanism.

Expand Down Expand Up @@ -1666,7 +1666,7 @@ Q: Should drivers support accessing Amazon EC2 instance metadata in Amazon ECS?
Changelog
=========

:2024-04-??: Clarify that driver should not validate ``saslSupportedMechs`` content.
:2024-04-19: Clarify that driver should not validate ``saslSupportedMechs`` content.
:2023-04-28: Added MONGODB-OIDC auth mechanism
:2022-11-02: Require environment variables to be read dynamically.
:2022-10-28: Recommend the use of AWS SDKs where available.
Expand Down
4 changes: 2 additions & 2 deletions source/mongodb-handshake/handshake.rst
Original file line number Diff line number Diff line change
Expand Up @@ -424,7 +424,7 @@ The ``speculativeAuthenticate`` reply has the same fields, except for the ``ok``
as seen in the conversation sections for MONGODB-X509, SCRAM-SHA-1 and SCRAM-SHA-256
in the `Driver Authentication spec <../auth/auth.md#supported-authentication-methods>`_.

Drivers MUST NOT validate whether content of the ``saslSupportedMechs`` attribute
Drivers MUST NOT validate the contents of the ``saslSupportedMechs`` attribute
of the initial handshake reply. Drivers MUST NOT raise an error if the
``saslSupportedMechs`` attribute of the reply includes an unknown mechanism.

Expand Down Expand Up @@ -679,4 +679,4 @@ Changelog
:2023-04-03: Simplify truncation for metadata
:2023-05-04: ``AWS_EXECUTION_ENV`` must start with ``"AWS_Lambda_"``
:2023-08-24: Added container awareness
:2024-04-??: Clarify that driver should not validate ``saslSupportedMechs`` content.
:2024-04-19: Clarify that driver should not validate ``saslSupportedMechs`` content.

0 comments on commit 76f2f65

Please sign in to comment.