-
Notifications
You must be signed in to change notification settings - Fork 625
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] More webhooks or more detailed webhook events #1739
Comments
It appears this may be a regression between version |
Example of a webhook no longer available in 4.0.3-1. Sample retrieved from 4.0.2-1
|
Upgraded to |
@jeffrey-e According to my tests, the events "markAsRead/markAsUnread" are correctly sent to webhoook endpoint (with TheHive 4.0.4) {
"_createdAt": 1612443034015,
"_createdBy": "me@thehive.local",
"_id": "~4112",
"_type": "Case",
"_updatedAt": null,
"_updatedBy": null,
"assignee": "me@thehive.local",
"fromAlert": {
"_id": "~26173600",
"source": "MISP-THP",
"sourceRef": "1",
"type": "misp"
},
[...]
} This field is also present in alert merging into case but the I'm not sure I understand your point regarding case reopen. The webhook event looks pretty clear: {
"base": true,
"details": {
"status": "Open"
},
"objectId": "~6832184",
"objectType": "case",
"operation": "update",
"requestId": "25a1b0c67de3c388:-451026a9:1776d157e19:-8000:508",
"rootId": "~6832184",
"startDate": 1612443666863,
"object": {
[...]
}
} |
Request Type
Bug / Feature Request
Work Environment
Problem Description
It appears we're getting fewer webhooks from TheHive4 than TH3. The webhooks that are sent don't contain enough detail to determine what action took place.
E.g.
We no longer get an
alert
webhook when an alert gets imported as a case. This is also the case when merging alerts into a case, there's only a generic"objectType": "case", "operation": "update"
webhook for which thedetails
show new field values but no reliable way to determine what happened.Another example is where a case is reopened, the only way to discern between a new or reopened case is to look for existing
resolutionStatus
andimpactStatus
field, though I'm not sure how robust that is.Steps to Reproduce
For example capturing all hooks with this configuration:
Create a case from an alert, merge
Possible Solutions
details
section of the webhook. Maybe the transition e.g.The text was updated successfully, but these errors were encountered: