[SERVER-71843] Do not allow dbStats with security token Created: 05/Dec/22 Updated: 18/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
Atlas Proxy does not send dbStats to mongod today, so Support Native Tenant Data Isolation in Mongod will not make it such that dbStats can accept a security token. Remove the override on allowedWithSecurityToken. Then, remove dbStats from the list of commands allowed with a security token here. Any tests that run dbStats in jstests/core and that currently run in the native_tenant_data_isolation_jscore_passthrough suite will fail, so we should add the tag "not_allowed_with_security_token" to the test and mention it runs with dbStats. |