When creating the webhook destination, allow the admin to set a flag so that the Certificate of the peer (the listener) is not verified.
This would allow self-signed certs to be used on the listener stack. (possibly because its self-hosted on a network that is not exposed to the outside world).
As yuri pointed out in my post asking if this is possible, the verification of the peer cert is hard-coded to true.
(post: https://forum.espocrm.com/forum/inst...sl-certificate)
It calls CURL: https://github.com/espocrm/espocrm/b...Sender.php#L90
the feature request is to add an option at webhook creation, that then controls the ssl peer cert validation flag in the curl call.
thanks!
This would allow self-signed certs to be used on the listener stack. (possibly because its self-hosted on a network that is not exposed to the outside world).
As yuri pointed out in my post asking if this is possible, the verification of the peer cert is hard-coded to true.
(post: https://forum.espocrm.com/forum/inst...sl-certificate)
It calls CURL: https://github.com/espocrm/espocrm/b...Sender.php#L90
the feature request is to add an option at webhook creation, that then controls the ssl peer cert validation flag in the curl call.
thanks!
Comment