-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a webhook event log #1314
Comments
This was referenced Nov 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add a webhook event log
Problem
Webhook events are not persisted in FusionAuth so you cannot view a historical record of which events were sent and if they webhook responded successfully, if the event was retried, etc.
Solution
We could add an event log for webhooks. Stripe has a similar feature and it allows you to view historical events with the full JSON body, view if an event has not yet been successfully received by a configured webhook etc.
Stripe recommends that a configured webhook only consume the event Id and then make an API request to Stripe to receive the event body. This way the event consumer does not have to trust the body that is sent and can trust the response from the Stripe API. Not sure this is necessary, but if we had an event log for webhook events we could add an API to respond to
GET
to support this workflow.In theory we could re-use our event log for this with a new event type. However this may not be the best solution. Ideally we'd just create a new table add a config to indicate how many records we should persist and then persist even event.
Alternatives/workarounds
N/A
Additional context
N/A
Related
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
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.
Documentation Tasks
The text was updated successfully, but these errors were encountered: