Update to clarify Actions examples #399
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
avanscoy
added
main-docs
nick-gagliardi
previously approved these changes
Dec 9, 2025
…assword reset flow
hazel-nut
reviewed
Dec 11, 2025
Comment on lines
+620
to
+621
| * The [`api.multifactor.enable`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-api-object#api-multifactor) Action trigger to handle both enrollment and issues configured MFA challenges at the end of the login flow. | ||
| * The [`event.user.multifactor`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-event-object) Actions trigger with the user's enrolled factors. |
Contributor
There was a problem hiding this comment.
"Actions trigger" or "Action trigger"? (not sure which one is the right way to refer to the product)
| * The [`event.user.multifactor`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-event-object) Actions trigger with the user's enrolled factors. | ||
|
|
||
| <Callout icon="file-lines" color="#0EA5E9" iconType="regular"> | ||
| Since `email` notifications are not an independent factor, the condition `const canPromptMfa = event.user.multifactor && event.user.multifactor.length > 0;` will return `false` if the user only has `email` as a factor. To learn more, read [Configure Email Notifications for MFA](/docs/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-email-notifications-for-mfa). |
Contributor
There was a problem hiding this comment.
Suggested change
| Since `email` notifications are not an independent factor, the condition `const canPromptMfa = event.user.multifactor && event.user.multifactor.length > 0;` will return `false` if the user only has `email` as a factor. To learn more, read [Configure Email Notifications for MFA](/docs/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-email-notifications-for-mfa). | |
| Since `email` notifications are not an independent factor, the condition `event.user.multifactor && event.user.multifactor.length > 0` will return `false` if the user only has `email` as a factor. To learn more, read [Configure Email Notifications for MFA](/docs/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-email-notifications-for-mfa). |
Comment on lines
+673
to
+679
| // It only makes sense to prompt for MFA when the user has at least one | ||
| // enrolled MFA factor. | ||
| const canPromptMfa = event.user.enrolledFactors && event.user.enrolledFactors.length >0; | ||
|
|
||
| if (shouldPromptMfa && canPromptMfa) { | ||
| api.authentication.challengeWithAny([ {type: "email"}, {type:"phone"} ]); | ||
| } |
Contributor
There was a problem hiding this comment.
Suggested change
| // It only makes sense to prompt for MFA when the user has at least one | |
| // enrolled MFA factor. | |
| const canPromptMfa = event.user.enrolledFactors && event.user.enrolledFactors.length >0; | |
| if (shouldPromptMfa && canPromptMfa) { | |
| api.authentication.challengeWithAny([ {type: "email"}, {type:"phone"} ]); | |
| } | |
| // It only makes sense to prompt for MFA when the user has at least one | |
| // enrolled MFA factor. | |
| const canPromptMfa = event.user.enrolledFactors && event.user.enrolledFactors.length > 0; | |
| if (shouldPromptMfa && canPromptMfa) { | |
| api.authentication.challengeWithAny([ {type: "email"}, {type:"phone"} ]); | |
| } |
| ### Adaptive MFA template | ||
|
|
||
| This template provides an example and starting point for how to build a custom business flow using individual risk assessments. | ||
| This template provides an example and starting point for how to build a custom business flow using individual risk assessments. In this example, we use: |
Contributor
There was a problem hiding this comment.
Suggested change
| This template provides an example and starting point for how to build a custom business flow using individual risk assessments. In this example, we use: | |
| This template provides an example and starting point for how to build a custom business flow using individual risk assessments. This example uses: |
| This template provides an example and starting point for how to build a custom business flow using individual risk assessments. | ||
| This template provides an example and starting point for how to build a custom business flow using individual risk assessments. In this example, we use: | ||
|
|
||
| * The [`api.multifactor.enable`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-api-object#api-multifactor) Action trigger to handle both enrollment and issues configured MFA challenges at the end of the login flow. |
Contributor
There was a problem hiding this comment.
Suggested change
| * The [`api.multifactor.enable`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-api-object#api-multifactor) Action trigger to handle both enrollment and issues configured MFA challenges at the end of the login flow. | |
| * The [`api.multifactor.enable`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-api-object#api-multifactor) Action trigger to handle both enrollment and issue configured MFA challenges at the end of the login flow. |
| ``` javascript | ||
| // It only makes sense to prompt for MFA when the user has at least one | ||
| // enrolled MFA factor. | ||
| const canPromptMfa = event.user.enrolledFactors && event.user.enrolledFactors.length >0; |
Contributor
There was a problem hiding this comment.
this change also uses event.user.enrolledFactors rather than event.user.multifactor, so it would be good to have an explanation of the difference or the reason for the change. is it because enrolledFactors counts email and multifactor doesn't?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.
Description
Requested update to clarify Adaptive MFA template and use of
emailas a secondary factor.References
Docs Request
Testing
Local
Checklist