Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
Description
Issues with the "Spec Test Format" section:
- client_side_enencryption_opts in the "Spec Test Format" section should be auto_encrypt_opts Fixed in https://github.com/mongodb/specifications/pull/623.
- auto_encrypt_opts should be autoEncryptOpts
- kms_providers should be kmsProviders
- schema_map should be schemaMap
- bypassAutoEncryption is missing from the list of auto encryption options
- Some operations don't have an object field. It should be documented that this defaults to "collection" if omitted.
Issues with the "Use as integration tests" section:
- The json_schema field should be mentioned to describe how the collection should be created.
- The description for setting up the test collection and inserting the test data uses the MongoClient created with the test's clientOptions. For tests with invalid encryption settings (e.g. "an insert with encrypted field on _id errors" in badQueries.json), using this client will cause the data insertion to fail. The test data should be inserted using a different client with no encryption enabled.
Issues with various tests:
- "operation fails with maxWireVersion < 8" in maxWireVersion.json - the error is expected to contain "Auto-encryption requires a minimum MongoDB version of 4.2" but the spec only says "Drivers MUST raise an error when attempting to auto encrypt a command if the maxWireVersion is less than 8" and does not specify the message.
- "getMore with encryption" in getMore.json - results field should be result.
- Corpus test step 9 - ClientEncryption has no schemaMap option.