Update web/docs/guides/auth/auth-twilio.mdx

This commit is contained in:
Joel Lee authored and GitHub committed 2022-06-06 11:33:14 +08:00
1 parent 6cbe621882
commit d63e60e7d7
1 file changed
+1 -1
+1 -1
View File
@@ -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`: