-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Client Side Encryption
-
None
-
Needed
-
Summary
It would be a good UX improvement to allow keyAltName in the encryptedFieldsMap instead of always requiring {{keyId}}s, and reduce the effort to get started with QE since 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.
- is depended on by
-
MONGOCRYPT-432 Allow keyAltName in encryptedFieldsMap
-
- In Code Review
-
- 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
-