You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
Release Notes
When using the Webhook test action in the FusionAuth admin UI, additional information will now be returned if the webhook returns a non-200 status code. This should make it simpler to debug your webhook integration. Prior to this change, the response would only indicate if the response was successful or not.
The text was updated successfully, but these errors were encountered:
Better error message when test webhook run from the admin UI fails
Problem
It would be nice to get a better error message when a webhook test, run from the webhook screen in the admin UI fails.
Currently, this is the message displayed when a webhook fails:
"The webhook returned an invalid response"
This is true whether the webhook is inaccessible, returns the wrong http status code, or simply fails to run to completion.
There are no additional debugging messages in the FusionAuth UI or log files.
Solution
It'd be great to provide more information. Ideally:
Alternatives/workarounds
Test the webhook with curl and see how it responds.
Related
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
Release Notes
When using the Webhook test action in the FusionAuth admin UI, additional information will now be returned if the webhook returns a non-200 status code. This should make it simpler to debug your webhook integration. Prior to this change, the response would only indicate if the response was successful or not.
The text was updated successfully, but these errors were encountered: