Actualmente realizamos la actualización de validacion y verificacion de los WebHook de Zoom, donde nos percatamos que los datos x-zm-signature y x-zm-request-timestamp que deberian venir en el header de los webhook segun la documentacion mencionada acontuacion Using webhooks no siempre estan llegando. Provocando que a la hora de verificar los webhook usando las cabeceras de Zoom (Zoom’s Header) falle, desconocemos si esta intermitencia de datos es un error o se debe a alguna información que no está presente en la documentación.
- Se inicia una reunion de Zoom
- Zoom envía Webhook hacia los Servidores PUCV
- Tratamos de obtener los datos x-zm-signature y x-zm-request-timestamp
- Los valores vienen en null
- No podemos autentificar la procedencia del Webhook
@software.dsic,
Thank you for reaching out. From what I understand, after validating your endpoint, you’re receiving events for a limited period and then they cease. Is that correct?
If this is the situation, please note that our system requires you to verify the webhook endpoint every 72 hours. If the challenge isn’t acknowledged appropriately, it might lead to disruptions in receiving the events.
is not correct, we have not stopped receiving the webhook events. What happens is that we are not receiving all the data to verify the origin of the webhook events, using the Zoom header verification. Link to the documentation Using webhooks
The data that we are not receiving constantly or intermittently are the variables x-zm-signature and x-zm-request-timestamp. Which are necessary to form the hash and validate the origin of the webhook.
thanks for the help