diff --git a/source/connect-to-mongo/network-compression.txt b/source/connect-to-mongo/network-compression.txt
index 2561c74..aa93070 100644
--- a/source/connect-to-mongo/network-compression.txt
+++ b/source/connect-to-mongo/network-compression.txt
@@ -23,9 +23,9 @@ of data passed over the network between MongoDB and your application.
The driver supports the following algorithms:
-- `Snappy <https://google.github.io/snappy/>`__: available in MongoDB 3.4 and later.
-- `Zlib <https://zlib.net/>`__: available in MongoDB 3.6 and later.
-- `Zstandard <https://github.com/facebook/zstd/>`__: available in MongoDB 4.2 and later.
+- `Snappy <https://google.github.io/snappy/>`__
+- `Zlib <https://zlib.net/>`__
+- `Zstandard <https://github.com/facebook/zstd/>`__
The driver tests against the following versions of these libraries:
@@ -95,4 +95,4 @@ guide, see the following API documentation:
- `MongoClient <{+driver-api+}/MongoClient.html>`__
- `createSnappyCompressor() <{+core-api+}/MongoCompressor.html#createSnappyCompressor()>`__
- `createZlibCompressor() <{+api-root+}//mongodb-driver-core/com/mongodb/MongoCompressor.html#createZlibCompressor()>`__
-- `createZstdCompressor() <{+core-api+}/MongoCompressor.html#createZstdCompressor()>`__
\ No newline at end of file
+- `createZstdCompressor() <{+core-api+}/MongoCompressor.html#createZstdCompressor()>`__
diff --git a/source/includes/mongodb-compatibility-table-java-rs.rst b/source/includes/mongodb-compatibility-table-java-rs.rst
index 63ba997..105a2f5 100644
--- a/source/includes/mongodb-compatibility-table-java-rs.rst
+++ b/source/includes/mongodb-compatibility-table-java-rs.rst
@@ -7,120 +7,36 @@
- MongoDB 8.1
- MongoDB 8.0
- MongoDB 7.0
- - MongoDB 6.1
- MongoDB 6.0
- - MongoDB 5.0
- - MongoDB 4.4
- - MongoDB 4.2
- - MongoDB 4.0
- - MongoDB 3.6
- * - 5.5
+ * - 5.2 to 5.5
- ✓
- ✓
- ✓
- ✓
- - ✓
- - ✓
- - ✓
- - ✓
- -
- -
-
- * - 5.2 to 5.4
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- -
* - 4.10 to 5.1
- ⊛
- ⊛
- ✓
- ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- * - 4.8 to 4.9
+ * - 4.7 to 4.9
- ⊛
- ⊛
- ⊛
- ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- * - 4.7
+ * - 4.0 to 4.6
- ⊛
- ⊛
- ⊛
- ⊛
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
-
- * - 4.3 to 4.6
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ✓
- - ✓
- - ✓
- - ✓
- - ✓
-
- * - 4.1 to 4.2
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ✓
- - ✓
- - ✓
- - ✓
-
- * - 4.0
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ⊛
- - ✓
- - ✓
- - ✓
* - 3.11 to 3.12
- ✗ [#v3-note]_
- ⊛
- ⊛
- ⊛
- - ⊛
- - ⊛
- - ⊛
- - ✓
- - ✓
- - ✓
.. [#v3-note] These driver versions are not compatible with MongoDB 8.1 or later because of an authentication issue. To learn more, see :ref:`java-rs-server-8.1-incompatibility`.
diff --git a/source/security/auth.txt b/source/security/auth.txt
index 7139700..a7c68f0 100644
--- a/source/security/auth.txt
+++ b/source/security/auth.txt
@@ -42,13 +42,8 @@ mechanisms.
Default Authentication Mechanism
--------------------------------
-In MongoDB 3.0, MongoDB changed the default authentication mechanism
-from ``MONGODB-CR`` to ``SCRAM-SHA-1``. In MongoDB 4.0, support for
-the deprecated ``MONGODB-CR`` mechanism was removed and ``SCRAM-
-SHA-256`` support was added.
-
To create a credential that authenticates by using the default
-authentication mechanism, regardless of server version, create a
+authentication mechanism, ``SCRAM-SHA-256``, create a
credential by using the ``createCredential()`` static factory method:
.. code-block:: java
@@ -73,33 +68,24 @@ authentication mechanism:
MongoClient mongoClient = MongoClients.create("mongodb://user1:pwd1@host1/?authSource=db1");
-For challenge and response mechanisms, using the default
-authentication mechanism is the recommended approach, as it makes
-upgrading from MongoDB 2.6 to MongoDB 3.0 more simple, even after
-upgrading the authentication schema. For MongoDB 4.0 users, using the
-default authentication mechanism is also recommended as the mechanisms are
-checked and the correct hashing algorithm is used.
+For challenge and response mechanisms, we recommend using the default
+authentication mechanism. This simplifies upgrades and ensures that the correct hashing
+algorithm is used.
SCRAM-Based Mechanisms
----------------------
-Salted Challenge-Response Authentication Mechanism (``SCRAM``) has been
-the default authentication mechanism for MongoDB since 3.0. ``SCRAM`` is
+Salted Challenge-Response Authentication Mechanism (``SCRAM``) is
based on the `IETF RFC 5802
<https://datatracker.ietf.org/doc/html/rfc5802>`__ standard that defines
best practices for implementation of challenge-response mechanisms for authenticating
-users with passwords.
-
-MongoDB 3.0 introduced support for ``SCRAM-SHA-1``, which uses the
-``SHA-1`` hashing function. MongoDB 4.0 introduced support for ``SCRAM-
-SHA-256`` which uses the ``SHA-256`` hashing function.
+users with passwords. MongoDB supports both ``SCRAM-SHA-1``, which uses the
+``SHA-1`` hashing function, and ``SCRAM-
+SHA-256``, which uses the ``SHA-256`` hashing function.
SCRAM-SHA-256
~~~~~~~~~~~~~
-Using this mechanism requires MongoDB 4.0 and
-``featureCompatibilityVersion`` to be set to 4.0.
-
To explicitly create a credential of type ``SCRAM-SHA-256``, use
the ``createScramSha256Credential()`` method:
@@ -149,7 +135,6 @@ To explicitly create a credential of type ``SCRAM-SHA-1``, use the
Or, you can use a connection string that explicitly specifies
``authMechanism=SCRAM-SHA-1``:
-
.. code-block:: java
MongoClient mongoClient = MongoClients.create("mongodb://user1:pwd1@host1/?authSource=db1&authMechanism=SCRAM-SHA-1");
@@ -159,12 +144,10 @@ MONGODB-CR
.. important::
- Starting in version 4.0, MongoDB removes support for the deprecated
+ MongoDB no longer supports the deprecated
MongoDB Challenge-Response (``MONGODB-CR``) authentication mechanism.
-
If your deployment has user credentials stored in a ``MONGODB-CR`` schema,
- you must upgrade to use a ``SCRAM``-based mechanism before you
- upgrade to version 4.0.
+ you must upgrade to a ``SCRAM``-based mechanism.
To explicitly create a credential of type ``MONGODB-CR`` use the
``createMongCRCredential()`` static factory method: