DOCSP-50019 - Remove EOL Server versions (#132)

(cherry picked from commit 0fa9d38)
(cherry picked from commit 6112917)
(cherry picked from commit e5d7536)

Author: mongoKart

source/includes/mongodb-compatibility-table-java-rs.rst

@@ -40,13 +40,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
@@ -71,33 +66,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:
 
@@ -147,7 +133,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");
@@ -157,12 +142,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: