[JAVA-4271] Use OP_MSG to authenticate if server supports OP_MSG Created: 09/Aug/21  Updated: 28/Oct/23  Resolved: 26/Jan/22

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.0

Type: Improvement Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: spec-compliance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
Server Compat: 5.1
Quarter: FY22Q4
Upstream Changes Summary:

DRIVERS-1873:
This ticket requires drivers to ensure that they are using OP_MSG for the authentication step if it is supported (maxWireVersion >= 6) as part of the process of establishing a new connection. Currently, some drivers still use OP_QUERY for the authentication step even if OP_MSG is supported. As support is being dropped for OP_QUERY, Once the server team implements SERVER-59085 in MongoDB using OP_QUERY for anything other than the first step of the handshake will raise an error. Thus, once that version is released we will be able to test this change by ensuring that the driver is able to successfully connect to that version server.
There are no spec test changes associated with this ticket.
Check out the Authentication Handshake spec for more details.


 Description   

DRIVERS Ticket Description
Script Target - If you can read this text, the script has failed


 Comments   
Comment by Jeffrey Yemin [ 26/Jan/22 ]

This work was already completed for the 4.3.0 release

Generated at Thu Feb 08 09:01:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.