-
Notifications
You must be signed in to change notification settings - Fork 14
Display localized error messages from webhooks #1725
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
Comments
Would one of the solutions outlined here work?
Or are you looking for something else? |
I'm aware of that option, but it's only one string. The idea here is to be able to return messages (or message IDs) for different types of issues in different webhooks, to be displayed in the hosted UI and the admin panel. The more general idea of returning data is also part of #1696. |
Any updates to this issue? I'm looking for this feature to verify email address before registration. I need to be able to return a custom error message based on a lookup from a database. |
@cch99 this work is not currently planned. Here's our general roadmap guidance: https://fusionauth.io/docs/v1/tech/core-concepts/roadmap |
Uh oh!
There was an error while loading. Please reload this page.
Display localized error messages from webhooks
Problem
When webhooks fail, a generic error message is displayed, which is not at all useful to an end user. I suggest allowing webhooks to return an error message to be displayed (see also #1696).
Solution
For example (in response to a failed webhook):
(this will obviously not work when the network request fails entirely)
Alternatives/workarounds
I don't think that there are any.
Additional context
#814 (comment)
#814 (comment)
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.
The text was updated successfully, but these errors were encountered: