dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-16 14:49:10 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'J0_update_twilio_and_workos_docs' of github.com:supabase/supabase into J0_update_twilio_and_workos_docs

Browse Source
This commit is contained in:
joel@joellee.org committed 2022-06-06 19:25:43 +08:00
2 parents 5b2b6fe7ff d63e60e7d7
commit 7d6139533a
1 file changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files
web/docs/guides/auth/auth-twilio.mdx
+2 -2
View File
@@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem'
## Overview
In this guide we'll show you how to authenticate your users with SMS based One-Time Password(OTP) tokens.
In this guide we'll show you how to authenticate your users with SMS based One-Time Password (OTP) tokens.
There are two reasons to use Supabase SMS OTP tokens:
@@ -93,7 +93,7 @@ Use the variable `.Code` in the template to display the OTP code. Here's an ![ex
### Using OTP with password based logins
In this scenario we'll be using the user's mobile phone number and a corrsesponding password as an alternative to signing up with an email address. Note: Please deeply consider the potential security implications when signing up with a combination ofphone and passsword. It is not uncommon for mobile phone numbers to be recycled by phone networks when users cancel their phone contracts or move countries, therefore granting access to the user's account to the subsequent owner of the phone number. In the near future Supabase will support multifactor auth, which will mitigate this risk, but for now you may want to consider allowing your users to recover their account by some other means in an emergency.
In this scenario we'll be using the user's mobile phone number and a corresponding password as an alternative to signing up with an email address. Note: Please deeply consider the potential security implications when signing up with a combination ofphone and passsword. It is not uncommon for mobile phone numbers to be recycled by phone networks when users cancel their phone contracts or move countries, therefore granting access to the user's account to the subsequent owner of the phone number. In the near future Supabase will support multifactor auth, which will mitigate this risk, but for now you may want to consider allowing your users to recover their account by some other means in an emergency.
Using supabase-js on the client you'll want to use the same `signUp` method that you'd use for email based sign ups, but with the `phone` param instead of the `email param`: