Email Verification Gate with TX Web-hooks Configured Prompts unexpected error

[jobannon]

Email Verification Gate with TX Web-hooks Configured Prompts unexpected error

Description

If you have configured two webhooks

• user.email.verified
• user.update

and you have configured the Tenant TX settings as All the Webhooks must succeed, when sending a user another verificationId at a Verification Gate landing page for email, a 500 error is returned.

Affects versions

Dev - 1.47.1

Steps to reproduce

Steps to reproduce the behavior:

1. Create a webhook
2. Turn on two events - user.update and user.email.verified
3. On the tenant level, under the webhooks tab, also enable only these events. Require that they succeed - All the webhooks must succeed.
4. Force your webhook to return a non-200 code to FusionAuth
5. Enable email verification (this affects both workflows; registration verification too, see below videos). Allow the user to change their email address at the verification gate page.
6. Enable Self Service User registration or add a user registration that needs to have email verification completed.
7. Arrive at a verification gate.
8. Adjust the email address of the user that would like to complete email verification.
9. See a 500 error.
10. Or try and upset to a new email address for verification and see a 500 error.

Expected behavior

Step 9/10 should not occur.
FusionAuth should return validation errors.

Platform

Dev setup. Client replicated.

Additional context

The FusionAuth syslogs do not log any information related to the 500 error.

We should review if any other affects registration verification (it does).

Failure Case #1

• With only user.email.verified webhook enabled
• and all the webhooks must succeed,
• and non-200 response returned from webhooks

FusionAuth should return a 400 validation error.

500.error.mp4

Failure Case #2

• With user.update and user.email.verified webhook enabled
• and all the webhooks must succeed,
• and non-200 responses returned from webhooks

FusionAuth should send the updated verification to the new email specified (end of video) and the last verification code should work (if not expired).

with-user-update-and-user.email.verified.mp4

Failure Case #3 -

• With user.update and user.registration.verified webhook enabled
• and all the webhooks must succeed,
• and non-200 responses returned from webhooks

FusionAuth should return a validation error and not a 500 error.

Registration-verification.mp4

Related

• Better Error Handling on Verify Email Webhook failure #2402