[SERVER-72809] Add FLE test coverage for NTDI Created: 12/Jan/23 Updated: 29/Oct/23 Resolved: 03/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | Mathis Bessa |
| 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: | Server Serverless 2023-01-23, Server Serverless 2023-02-06 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We should be adding a jstest that will make sure of field level encryption and the use of tenancy awareness by passing a `$tenant` to the queries. The current FLE2 jstests used in enterprise can be use as a foundation to make encrypted queries to a mongod. The cpp client code used to create an encrypted client is only used for testing purposed and doesn't need to be tenant aware. A mongoshell (client) doesn't understand nor know the concept of `$tenant` therefor, for the purpose of testing, we need to make sure that the FLE logic is properly executed on the mongod regardless of that constraint. We do not need to test specifically the encryption itself but make sure that the encryption is being executed for a specific tenant and not for others. |
| Comments |
| Comment by Githook User [ 03/Feb/23 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |