You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2019. It is now read-only.
We (CS) are building some rules for using Passwordless as MFA.
Right now, we are going to hack Lock in order to initialise it in the second step (the view which asks for code in SMS) forcing the state of it as if the first step was already completed.
It would be nice to have the ability to set the phone number when we show it, so lock takes care of sending the SMS and asking for the code. Something like this:
var lock = new Auth0LockPasswordless(cid, domain);
lock.sms({phone_number:’….’});
The text was updated successfully, but these errors were encountered:
Something to have in mind, it shouldn't start a login process. We don't care about authentication in this case, we need a way to verify the code.
So in this particular implementation, we just need to call the callback with the result of the request to /passwordless/verify and this is particularly because we can't start a new authentication process if we stopped the rules pipeline with a redirect (used for the MFA rule).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We (CS) are building some rules for using Passwordless as MFA.
Right now, we are going to hack Lock in order to initialise it in the second step (the view which asks for code in SMS) forcing the state of it as if the first step was already completed.
It would be nice to have the ability to set the phone number when we show it, so lock takes care of sending the SMS and asking for the code. Something like this:
The text was updated successfully, but these errors were encountered: