[SERVER-55995] Rewrite audit/transactions.js to use the AuditSpooler correctly Created: 09/Apr/21 Updated: 29/Oct/23 Resolved: 10/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shreyas Kalyan | Assignee: | Shreyas Kalyan |
| 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-04-19, Security 2021-05-03, Security 2021-05-17 | ||||
| Participants: | |||||
| Linked BF Score: | 29 | ||||
| Description |
|
Currently, the test in transactions.js is just calling getNextEntry() and examining the next line in the audit spooler to see that the entry that it expects is present. However, this uses the incorrect assumption that there are no other processes auditing at the time. This should be fixed to use the AuditSpooler functionality like assertEntry and findEntry. |
| Comments |
| Comment by Githook User [ 10/May/21 ] |
|
Author: {'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}Message: |
| Comment by Shreyas Kalyan [ 07/May/21 ] |
|
code review (enterprise): https://mongodbcr.appspot.com/778470080/ |