As part of the Syniverse continuous effort to improve our products and elevate our security posture, we have updated our webhook workflow.
The Event Subscriptions Service (ESS) Delivery Configuration now requires the webhook URL domain to be whitelisted.
This action introduces governance, and oversight.
Once the request to whitelist the webhook URL domain has been processed, the completion of the configuration requires up to 48 hours to complete.
What happened if the webhook is not whitelisted?
Although it is possible to register a Delivery Receipt webhook before Whitelisting the URL, the effect in the webhook is that, in case of an event, the notification will be blocked, preventing the webhook to receive the event callback.
This case can be confirmed by querying the Events in the SDC Event Viewer where the event can be reviewed including the details on every delivery attempt.
When the Delivery Configuration is not Whitelisted, the Event Viewer will show you the event as FAILED:
The Gear / View Details option you can access by click the gear, shows the Event details including the delivery attempts:
Event Delivery Attempts can be found in the Event detail information:
When the URL is not whitelisted, it cannot be retrieved from the whitelist. In this case, the event error details will display as below:
Authentication and Encryption servers URLs?
In case your webhook server makes use of authentication and/or encryption methods that need access to key servers, these servers need to be whitelisted.
How to whitelist your webhooks URLs?
To whitelist your webhook URL, please open a support ticket requesting the whitelisting of your webhooks domains.
After 24 to 48 hours, your webhooks will be ready to go.
0 Comments