[SERVER-64100] Prohibit encrypted fields and json schema with encrypted fields in create collection Created: 01/Mar/22 Updated: 29/Oct/23 Resolved: 28/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Shreyas Kalyan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Security 2022-03-21, Security 2022-04-04 |
| Participants: |
| Description |
|
To reduce scope, it is difficult to verify if a user has specified encryptedField and JSON schema for the same field in createCollection. We also do not want users to have FLE 1 deterministic and FLE 2 in the same collection. As a result, we are going to block users from using them at the same time. In DatabaseImpl::userCreateNS,if collectionOptions.encryptedFieldConfig.has_value(), remove MatchExpressionParser::AllowedFeatures::kEncryptKeywords from allowedFeatures in MatchExpressionParser::parse. |
| Comments |
| Comment by Githook User [ 25/Mar/22 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: |
| Comment by Githook User [ 25/Mar/22 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: |