[DRIVERS-2372] Add createKey to ClientEncryption as an optional feature Created: 27/Jun/22 Updated: 28/Jun/22 Resolved: 28/Jun/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Client Side Encryption |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Unknown |
| Reporter: | Ezra Chung | Assignee: | Ezra Chung |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Driver Changes: | Not Needed | ||||||||||||
| Description |
SummaryThe initial Key Management API spec in In order to minimize friction with the Node driver, it is proposed that createKey() be added back to the spec as an optional feature, with the suggestion that Drivers which have not yet implemented createKey() or released the Key Management API continue to make an effort to exclude createKey() for reasons stated in MotivationWho is the affected end user?Primarily the Node driver and its downstream users. Other drivers currently implementing the Key Management API are also involved. How does this affect the end user?Leaving createKey() removed from the spec would means Node is non-conforming. How likely is it that this problem or use case will occur?The issue primarily affects the Node driver and its downstream users. If the problem does occur, what are the consequences and how severe are they?Requiring Node to remove createKey() for spec conformance may have undesirable and far-reaching consequences for downstream users of both Node and mongosh. Is this issue urgent?Somewhat. No actual effort is required by this ticket w.r.t. Is this ticket required by a downstream team?Needed by the Node Driver. Is this ticket only for tests?No. This impacts the permitted interface for ClientEncryption as part of the Key Management API. |