[SERVER-69369] Ensure collMod command works in multitenant environment Created: 01/Sep/22 Updated: 29/Oct/23 Resolved: 11/Oct/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: | Didier Nadeau |
| 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-10-17 | ||||
| Participants: | |||||
| Description |
|
Ensure the collMod command can be run with a security token and with $tenant. The command itself should already thread the tenantId through the execution path, but we may need to thread it through the auth system for the command, i.e. we'll need to construct the NamespaceString for the view using the DatabaseName object when checking whether the user is authorized to modify the view. Add a test to both of native_tenant_data_isolation_basic js tests. |
| Comments |
| Comment by Githook User [ 11/Oct/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |