[SERVER-83411] Retrieving encryption schema should include tenancy Created: 17/Nov/23 Updated: 22/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ntdi_releasability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Story Points: | 1 | ||||
| Description |
|
Today we strip the tenantId information when we access the schema containing the encryption information. We should confirm and make the change to include the tenantId here. We should also update the jstest related to FLE to use an unsigned security token and prefixed db in order to simulated AP's behavior. |