[DRIVERS-1960] Make read concern and write concern for key vault configurable Created: 20/Oct/21 Updated: 15/Nov/22 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Client Side Encryption |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Driver Changes: | Needed | ||||||||||||
| Description |
SummaryMake read concern and write concern for key vault configurable. MotivationClient Side Encryption requires majority read and write concern for operations:
This prohibits use of clusters where majority read concern has been disabled by adding an option to the encryption settings allowing the read concern to be specified. Who is the affected end user?Operations teams that have disabled majority read concern as per our documentation. How does this affect the end user?End users may be blocked if dev ops are not willing or able to re-enable majority read concern. But there is a workaround: enable majority read concern. How likely is it that this problem or use case will occur? We've heard about this from 2 users since the release of field level encryption, so it does not seem particularly common. If the problem does occur, what are the consequences and how severe are they?Unable to use field level encryption Is this issue urgent?Unclear whether it's urgent for the user that reported it. Is this ticket required by a downstream team?No Is this ticket only for tests?No |
| Comments |
| Comment by Jeffrey Yemin [ 20/Oct/21 ] |
|
Alternatives considered:
|