[SERVER-39249] Reject commands which reference an encrypted field with non-static keyId Created: 29/Jan/19 Updated: 29/Oct/23 Resolved: 29/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Ted Tuckman |
| 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: | Query 2019-03-11, Query 2019-03-25, Query 2019-04-08 | ||||||||
| Participants: | |||||||||
| Description |
|
JSON Schema allows an encrypted field with a keyId which points to another field in the document. References to such a field is only allowed in the insert command. |
| Comments |
| Comment by Githook User [ 29/Mar/19 ] |
|
Author: {'name': 'Ted Tuckman', 'username': 'TedTuckman', 'email': 'ted.tuckman@mongodb.com'}Message: |
| Comment by David Storch [ 20/Feb/19 ] |
|
nicholas.zolnierz ted.tuckman, I think it would be easiest to make this change specifically for MatchExpression first. We can have follow-up patches which do something similar for other parts of MQL. |