Triggering the "gd_send_email_verification" and "gd_auth_email_verification" Events in Auth0 Tenant Logs

This article explains the conditions that trigger the gd_send_email_verification and gd_auth_email_verification events in Tenant Logs.

• Adaptive Multi-Factor Authentication (MFA)
• Email Verification
• Universal Login

This event is generated only when a specific combination of security and user configurations is met. It is part of the "Email Challenge" flow within Adaptive MFA, which is triggered as a form of step-up authentication under high-risk conditions.

The appearance of the gd_send_email_verification and gd_auth_email_verification event logs is expected behavior when the following conditions are met:

• Adaptive MFA is enabled. This is set in the Auth0 Dashboard by navigating to Security > Multi-factor Auth and setting Require Multi-factor Auth to Use Adaptive MFA.
• An MFA challenge is triggered because the risk assessment for a login is high.
• The user attempting to sign in has no enrolled MFA factors other than Email.

Those logs are recorded after sending a verification email (gd_send_email_verification) and a user successfully completes an email verification step (gd_auth_email_verification) during a high-risk login attempt, as determined by Adaptive MFA.

The sequence of events is as follows:

1. A user attempts to log in to an application.
2. Auth0's Adaptive MFA feature assesses the login attempt and determines it to be high-risk.
3. The user is prompted for a second factor of authentication, but has not yet enrolled in any MFA factors.
4. As a fallback mechanism, a one-time password (OTP) is sent to the user's registered email address.
5. The gd_send_email_verification log is recorded in the tenant logs.
6. The user is prompted to enter the OTP to verify their identity.
7. The user successfully enters the correct OTP.
8. The user's email address is marked as verified (email_verified: true).
9. The gd_auth_email_verification log is recorded in the tenant logs to reflect the successful email verification.

For more details, see Adaptive MFA.