[SERVER-83151] NTDI _setSecurityToken helper shouldn't set a token on global DBs Created: 10/Nov/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: | Didier Nadeau | Assignee: | Didier Nadeau |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Service Arch 2023-11-27 |
| Participants: |
| Description |
|
The _setSecurityToken helper created to use security token always set the security token on messages. This forces us to set and clear the token repeatedly to avoid setting it on commands that shouldn't include a tenant. |
| Comments |
| Comment by Didier Nadeau [ 13/Nov/23 ] |
|
Investigating other solutions as this helper is also needed outside of NTDI (where the token is used to authenticate rather than provide the tenant). |