-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Client Side Encryption
-
None
-
Needed
-
Summary
Support specifying keys by "keyAltName" for QE when using encryptedFieldsMap.
Motivation
Requested in MONGOCRYPT-432 and scoped in WRITING-33646. libmongocrypt translates the keyAltName to keyId to require no driver or server changes.
Who is the affected end user?
Users of QE.
How does this affect the end user?
Quoting MONGOCRYPT-342:
it avoids the chicken-and-egg problem where users first need to create the keys using a half-autoencryption-configured MongoClient before being able to create the main MongoClient instance.
How likely is it that this problem or use case will occur?
Certain?
If the problem does occur, what are the consequences and how severe are they?
Confusion.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No?
Is this ticket only for tests?
No? It only requires a libmongocrypt upgrade and test sync.
Acceptance Criteria
- Add spec test to verify keyAltName can be specified in encryptedFieldsMap
- Upgrade libmongocrypt to 1.18.0
- is depended on by
-
MONGOCRYPT-432 Allow keyAltName in encryptedFieldsMap
-
- Closed
-
- split to
-
CDRIVER-6238 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
CSHARP-5874 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
CXX-3417 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
GODRIVER-3813 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
JAVA-6096 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
NODE-7433 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
PHPLIB-1786 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
PYTHON-5720 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
RUBY-3773 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-
-
RUST-2360 Allow keyAltName in encryptedFieldsMap
-
- Blocked
-