From 1be124152219258ccef828965cca26bf0417115f Mon Sep 17 00:00:00 2001 From: Dan Moore Date: Fri, 12 Jan 2024 16:00:46 -0700 Subject: [PATCH] update TOTP export (#2818) * update TOTP export * corrected noun agreement --- astro/src/content/docs/lifecycle/migrate-users/bulk/auth0.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/lifecycle/migrate-users/bulk/auth0.mdx b/astro/src/content/docs/lifecycle/migrate-users/bulk/auth0.mdx index d3fbc85495..8224e2a59d 100644 --- a/astro/src/content/docs/lifecycle/migrate-users/bulk/auth0.mdx +++ b/astro/src/content/docs/lifecycle/migrate-users/bulk/auth0.mdx @@ -322,7 +322,7 @@ The former will [trigger an MAU increment](/docs/get-started/core-concepts/users While you can't generate a fixed set of recovery codes, once MFA has been enabled for a user, you can [retrieve the recovery codes](/docs/apis/two-factor#retrieve-recovery-codes). -If your user uses TOTP, where they provide a one time code provided by an application like Google Authenticator, you'll need to request the initial secret for your users from Auth0 by opening a support ticket with them. +If your user uses TOTP for MFA, where they provide a one time code provided by an application like Google Authenticator, you'll need to re-enroll them. As of Oct 2022, [Auth0 doesn't support export of TOTP secrets](https://community.auth0.com/t/can-mfa-secrets-be-exported/91656). If your users use a different method unsupported by FusionAuth, then you should map the Auth0 method to a FusionAuth method.