[SERVER-54942] Relax audit_import_collection test assertion check Created: 04/Mar/21 Updated: 29/Oct/23 Resolved: 08/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Varun Ravichandran | Assignee: | Varun Ravichandran |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 2021-03-08 | ||||
| Participants: | |||||
| Linked BF Score: | 24 | ||||
| Description |
|
Currently, the audit_import_collection.js test checks that the audit event emitted right after the `importCollection` command is of atype `importCollection`. Due to work by the Security team to increase the coverage of audit events (namely `createIndex`), this is no longer guaranteed to be true and is responsible for BF-20177. The assertion check should be relaxed to use `audit.assertEntry()`, which will check that the appropriate `importCollection` audit entry has been emitted within a default timeout after the `importCollection` command has run. |
| Comments |
| Comment by Githook User [ 05/Mar/21 ] |
|
Author: {'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}Message: |