-
Type: Task
-
Resolution: Done
-
Priority: Unknown
-
None
-
Component/s: Client Side Encryption
-
None
-
Needed
-
Summary
createEncryptedCollection (DRIVERS-2312) should not accept keyAltNames. The problem is that if keyAltNames is given and createEncryptedCollection creates >1 key, then the method will always fail because of a duplicate key error.
MONGOCRYPT-432 would allow createEncryptedCollection to create keys with different keyAltNames through encryptedFieldsMap/encryptedFields.
Motivation
Who is the affected end user?
Users will be confused by duplicate key errors.
How does this affect the end user?
Users that want to create keys with keyAltNames will need to call createDataKey manually.
How likely is it that this problem or use case will occur?
Likely if keyAltNames is given.
Is this issue urgent?
Would be good to remove the keyAltNames parameter before users encounter this issue.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
No.
- related to
-
MONGOCRYPT-432 Allow keyAltName in encryptedFieldsMap
- Backlog
- split to
-
CDRIVER-4568 createEncryptedCollection should not accept keyAltNames or keyMaterial
- Closed
-
CSHARP-4514 createEncryptedCollection should not accept keyAltNames or keyMaterial
- Closed
-
CXX-2646 createEncryptedCollection should not accept keyAltNames or keyMaterial
- Closed
-
GODRIVER-2746 createEncryptedCollection should not accept keyAltNames or keyMaterial
- Closed
-
JAVA-4865 createEncryptedCollection should not accept keyAltNames or keyMaterial
- Closed
-
MOTOR-1092 createEncryptedCollection should not accept keyAltNames
- Closed
-
NODE-5029 createEncryptedCollection should not accept keyAltNames or keyMaterial
- Closed
-
PHPLIB-1078 createEncryptedCollection should not accept keyAltNames
- Closed
-
PYTHON-3589 createEncryptedCollection should not accept keyAltNames
- Closed
-
RUBY-3214 createEncryptedCollection should not accept keyAltNames
- Closed
-
RUST-1593 createEncryptedCollection should not accept keyAltNames
- Closed