First updates for Advanced Factor Config - #1678
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Summary
Errors per inputErrors in main/docs/secure/multi-factor-authentication/auth0-guardian.mdx
Errors in main/docs/secure/multi-factor-authentication/auth0-guardian/guardian-for-android-sdk.mdx
Errors in main/docs/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-sms-voice-notifications-mfa.mdx
Redirects per inputRedirects in main/docs/secure/multi-factor-authentication/auth0-guardian/guardian-for-android-sdk.mdx
Redirects in main/docs/secure/multi-factor-authentication/authenticate-using-ropg-flow-with-mfa/enroll-challenge-sms-voice-authenticators.mdx
Redirects in main/docs/secure/multi-factor-authentication/configure-cisco-duo-for-mfa.mdx
Redirects in main/docs/secure/multi-factor-authentication/manage-mfa-auth0-apis/manage-authenticator-factors-mfa-api.mdx
Redirects in main/docs/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-sms-voice-notifications-mfa.mdx
Redirects in main/docs/secure/multi-factor-authentication/step-up-authentication/configure-step-up-authentication-for-web-apps.mdx
|
andy317fe301f8c7
left a comment
There was a problem hiding this comment.
Reviewed against the current head commit and cross-checked the OTP/remember-me ranges directly against the live atko-cic/api2 schema and atko-cic/auth0-server code (not just the PRD). A few earlier concerns (SMS OTP length lower bound, TOTP-app digit count, a typo) are already fixed in this revision. Left inline comments on what's still open — mostly range/units accuracy and two documentation gaps for settings that are already live via the Management API but not yet documented here.
| 1. Navigate to [**Auth0 Dashboard > Security > Multi-Factor Auth**](https://manage.auth0.com/#/multifactor-auth) and select **Email**. | ||
| 2. Configure the following: | ||
| - **Verification Code Length**: Enter a value between 4 and 10 digits. | ||
| - **Verification Code Lifetime**: Enter a value between 5 and 60 minutes. |
There was a problem hiding this comment.
Same issue as the range table above — "5 and 60 minutes" should be "0.5 and 60 minutes" if the true floor is 30 seconds, pending confirmation from eng on whether the Dashboard enforces a stricter minimum than the API.
There was a problem hiding this comment.
Pending Engineering. Auth0 Dashboard is still showing 5 to 60 minutes.
| 5. Configure **Idle Trusted Browser Lifetime** in days or hours. | ||
| 6. Configure **Maximum Trusted Browser Lifetime** in days or hours. | ||
| </Tab> | ||
| <Tab title="Auth0 Actions"> |
There was a problem hiding this comment.
This section ("Change frequency of MFA prompts") only has Dashboard and Actions tabs. There's a real, GA Management API path for these same settings that isn't documented anywhere on this page:
GET/PUT /api/v2/guardian/settings(gated behindmfa_advanced_factor_configflag +update:tenant_settingsscope)- Fields
mfa_session_inactivity_timeout/mfa_session_overall_timeout(seconds), nested underuniversal_login.* - Confirmed the reader (
auth0-server'sbuildTenantTimeoutConfig) and writer (this api2 endpoint) are aligned today — the field-mismatch bug between them was fixed by PR auth0-server#19166, merged 2026-08-12.
Suggest adding a third "Management API" tab here with GET/PUT + JSON examples, matching the pattern already used in the OTP-settings sections on the email/SMS pages, and noting the feature-flag/entitlement requirement.
Description
Update existing pages with AFC, Code Length and Code Lifetime
References
Testing
Checklist
CONTRIBUTING.md.