Verification Email question

Help
,
21

Is it even possible to update the user data within a hook then?

In general, yes, you’d just need to hardcode the Auth0 tenant domain and get the access token dynamically. However, for the given scenario (with the email_verified flag), I’m running into some limitations.

I did some testing myself just now; in the pre-user registration hook, the user isn’t persisted yet, therefore the updateUser would fail, because there’s not user id available yet.

Therefore, the updateUser call only works in a post-user-reg hook. I tested it and it updates the email_verified attribute for the user correctly, however, it seems to come in too late. The email verification mail still get’s send. Which isn’t surprising, because the post-user-reg hook runs asynchronously to the signup flow.

So, right now, unfortunately I don’t have a good solution to avoid the email verification mail delivery conditionally on signup.

1 Like
22

Ok thank you. I will look into a different route.

1 Like
23

I’d also recommend to send the verification always, because otherwise, how to send a password reset mail? Shouldn’t it follow the same logic as sending a newsletter - how can you be sure to send it to the right person and not “spamming” an innocent user?