[SERVER-67423] Include tenantId in requests sent with DBDirectClient to have user management cmds work Created: 21/Jun/22 Updated: 29/Oct/23 Resolved: 30/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Sophia Tan |
| 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 2022-09-05, Server Serverless 2022-09-19, Server Serverless 2022-10-03 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently the user management commands cannot work with $tenant in multitenancy_test_authzn.js. Commands like createUser et. al. can ONLY be called by highly privileged local users making use of the $tenant field, so passing through to the underlying command only makes sense with a $tenant style request, not with a security token based request. The root cause is the tenant id of a command request is not thread down through DBDirectClient. In this ticket, DBDirectClient will be changed to fill $tenant field of OpMsg with tenant id for sending to local service entry point. The $tenant can be used here because the DBDirectClient has internal privileges automatically.
|
| Comments |
| Comment by Githook User [ 30/Sep/22 ] |
|
Author: {'name': 'Sophia Tan', 'email': 'sophia_tll@hotmail.com', 'username': 'sophiatll'}Message: |