[DRIVERS-2360] Ensure "does not fail" in CSE Prose Test 13 accounts for (no) matching documents Created: 16/Jun/22 Updated: 07/Apr/23 Resolved: 07/Apr/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Ezra Chung | Assignee: | Ezra Chung |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Key Management API | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Quarter: | FY23Q2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | Ensure implementations of Client Side Encryption Prose Test 13 assert the result of addKeyAltName() operations as specified in 50e26feb. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
SummaryThe current wording in Client Side Encryption Prose Test 13 requires certain addKeyAltName() operations "does not fail". However, this description does not take into account potential failure to find a matching document to add a keyAltName to, which also satisfies the "does not fail" condition (returning a null value instead of the previous state of the matched key document). The prose test description should be improved to ensure the addKeyAltName() operations are succeeding because it successfully found and added a keyAltName to a matching document, not because it did not find a matching document. MotivationWho is the affected end user?Drivers that have implemented, or will implement, CSE Prose Test 13. How does this affect the end user?Drivers' implementation of CSE Prose Test 13 will need to assert the result of addKeyAltName() operations include the keyAltName added in a previous operation if they are not already doing so. How likely is it that this problem or use case will occur?During implementation, Drivers might construct an incorrect filter argument to addKeyAltName() and fail to correctly test the success conditions intended by the prose test. This is more likely on Drivers that must convert to/from Native UUID Types. If the problem does occur, what are the consequences and how severe are they?Minor. Is this issue urgent?No. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Githook User [ 16/Jun/22 ] |
|
Author: {'name': 'Ezra Chung', 'email': '88335979+eramongodb@users.noreply.github.com', 'username': 'eramongodb'}Message: |