Description
This article describes how to check webhooks functionality on the firewall.
Solution
For the first time, Webhooks was introduced in version 6.0 of FortiOS.
It represent an HTTP request to some endpoint, as a result to specific action. Consider them as callback for some triggers. Usually the content of such request is a JSON document, but it is not limited to this.
If the payload is sent in JSON document, it will be required to specify the content-type:
content-type: application/json
This article describes how to check webhooks functionality on the firewall.
Solution
For the first time, Webhooks was introduced in version 6.0 of FortiOS.
It represent an HTTP request to some endpoint, as a result to specific action. Consider them as callback for some triggers. Usually the content of such request is a JSON document, but it is not limited to this.
If the payload is sent in JSON document, it will be required to specify the content-type:
content-type: application/json
In the webhook configuration section, it is possible to customize the HTTP header, like JWT token for authentication.
Using HTTP endpoint give the control to sniff outgoing interface and check the format and content of sending HTTP request.
On the GUI, there is context menu with option to run stitch (in this case with webhooks)
On the GUI, there is context menu with option to run stitch (in this case with webhooks)
For more information of what is done while the run of automation stitch, enable debug on ‘autod’ daemon:
# dia deb application autod -1
# dia deb en
