JAVA-6171 upgrade libcrypt to 1.17.3#1947
Merged
strogiyotec merged 4 commits intomongodb:mainfrom Apr 23, 2026
Merged
Conversation
nhachicha
pushed a commit
to nhachicha/mongo-java-driver
that referenced
this pull request
Apr 29, 2026
* JAVA-6171 upgrade libcrypt to 1.17.3 * Update CSF<BS>LE $lookup prose test case 8 --------- Co-authored-by: Almas Abdrazak <abdrazak.almas@mongodb.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JAVA-6171 upgraded libcrypt version to latest 1.17.3
The test case has been changed
Old expectation (libmongocrypt < 1.17.0):
libmongocrypt refused to build the command at all. It threw a client-side MongoCryptException with the message "not supported" before reaching the server
Since 1.17.0 library introduced a new feature, according to release notes
The change
Our CSFLE collection has an actual encryption schema (not just a plain JSON-schema validator), so the server still rejects the mixed request but now it's a server-side MongoCommandException