Summary

Support the QE Text $encStrNormalizedEq operator with explicit encryption.

Motivation

QE explicit encryption currently supports these values for queryType:

• "prefixPreview" for $encStrStartsWith
• "suffixPreview" for $encStrEndsWith
• "substringPreview" for $encStrContains

WRITING-8865 documents the $encStrNormalizedEq. But the ClientEncryption.encrypt API does not produce the necessary text exact payload.

Who is the affected end user?

Users of QE explicit encryption.

How does this affect the end user?

QE text prefix, suffix, and substring queries are currently possible. Cannot do QE text exact queries.

How likely is it that this problem or use case will occur?

Unsure. Found when using Claude to generate tests of QE text explicit encryption.

If the problem does occur, what are the consequences and how severe are they?

Feature incompleteness. Despite the footguns of explicit encryption (DRIVERS-3255) explicit encryption is still a means of testing QE without auto encryption. Auto encryption requires enterprise or Atlas.

Is this issue urgent?

Yes? I think this should be done before DRIVERS-3408.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No.

Acceptance Criteria

• A test using explicit encryption with the $encStrNormalizedEq should succeed.