[SERVER-71861] Allow killOp with security token Created: 05/Dec/22 Updated: 29/Oct/23 Resolved: 21/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-12-26 |
| Participants: |
| Description |
|
We should support the killOp command with a security token. Override allowedWithSecurityToken to return true for mongod's killOp command. Note that we don't want to override on KillOpCmdBase, because we'd enable it mongos/mongoq as well by doing so. The command only uses the dbName to log, so we shouldn't need any other changes to the command execution path. Then, remove the tag "not_allowed_with_security_token" from any jstests/core tests that are tagged only because they run killOp. We can easily find which tests are currently excluded because of killOp only by grepping for "The test runs commands that are not allowed with security token: killOp." |
| Comments |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |