[SERVER-80925] Filter out $tenant when VTS has valid tenantId from security token Created: 08/Sep/23 Updated: 13/Nov/23 Resolved: 13/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hugh Tong (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
Ensure createWithValidatedTenancyScope only builds the $tenant field when VTS is populated from $tenant, since it is invalid to have tenantIds come from both $tenant and the security token. This was lost when we started passing serialization context into createWithValidatedTenancyScope and create, but this condition should still hold whether or not a valid serialization context is passed in. |
| Comments |
| Comment by Didier Nadeau [ 13/Nov/23 ] |
|
Not applicable as we'll remove all code related to $tenant. |