[SERVER-85893] Always have a valid original token when constructing a ValidatedTenancyScope Created: 29/Jan/24 Updated: 02/Feb/24 Resolved: 02/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | Sophia Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ntdi_code_quality, ntdi_must_have | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service Arch 2024-02-05 | ||||||||
| Participants: | |||||||||
| Description |
|
We should guarantee that there is always a valid _originalToken when constructing a ValidatedTenancyScope.Otherwise, when serializing a VTS, the tenant id information will be dripped off. In this task, we will change the TrustedForInnerOpMsgRequestTag version (code) to set the `_originalToken` with proper value. |
| Comments |
| Comment by Githook User [ 02/Feb/24 ] |
|
Author: {'name': 'Sophia Tan', 'email': 'sophia_tll@hotmail.com', 'username': 'sophiatll'}Message: GitOrigin-RevId: f4d4579ee527b9a071cc62d0143210a2a7bc128e |