[SERVER-63464] Create Collection restrictions with encrypted fields Created: 09/Feb/22 Updated: 29/Oct/23 Resolved: 11/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Erwin Pe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2022-02-21 | ||||
| Participants: | |||||
| Linked BF Score: | 33 | ||||
| Description |
|
Create collection should fail if we try to use encrypted fields with views or timeseries collections. It should also fail if created on a standalone instance. (Call getReplicationMode on ReplicationCoordinator) |
| Comments |
| Comment by Githook User [ 11/Feb/22 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |