From 685b5e97d4f00507a4aea75849bfac2a55f43a8f Mon Sep 17 00:00:00 2001 From: Joel Lee Date: Wed, 14 Dec 2022 02:52:31 +0530 Subject: [PATCH] Update apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx Co-authored-by: Kang Ming --- apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx b/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx index e705b91bb21..9bb5f1a3059 100644 --- a/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx +++ b/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx @@ -38,7 +38,7 @@ The first portion of `otpauth://totp/supabase.io` describes the protocol and is In the event that the user faces difficulties entering a QR code the user can also opt to manually type the secret into the authenticator device. -## MFA Flows: Enrolment and Verification +## MFA Flows: Enrollment and Verification An MFA flow can be broken into two key steps: Enrollment and Verification. During the *Enrollment* process Supabase Auth exchanges a randomly generated secret with the user’s authenticator application. During the *Verification* process, the device makes use of the timestamp together with the secret to produce a six digit code that the server can verify.