Clee/docs 240 #19
Clee/docs 240 #19
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Couple quick asks:
In order to send SMS messages, you must first add your credit card, this is to limit fraud/spam and in case there are incidental charges. |
src/components/Authenticate.tsx
Outdated
| @@ -25,6 +25,8 @@ const Authenticate = () => { | |||
| if (stytch && !user && isInitialized) { | |||
| const token = searchParams.get("token"); | |||
| const stytch_token_type = searchParams.get("stytch_token_type"); | |||
| const code = searchParams.get("code"); | |||
There was a problem hiding this comment.
Is this code necessary?
An OTP flow (when using the pre-built UI) doesn't involve a redirect, and thus won't hit this route. The OTP code should be entered (and auth'd) all in the login component completely by the JS SDK.
There was a problem hiding this comment.
Ah you're right, I've looked through the JS SDK and see that we can grab the user input as part of the state to pass to the authenticate call. Updated!
There was a problem hiding this comment.
To put a finer point on it, no backend authenticate call is necessary for OTP when you're using our pre-built UI components. Unlike with EML or OAuth, no redirect happens as part of the authentication flow, so the user will never hit the redirect.
So for adding OTP to this app, all we'll need to do is the work in Login.tsx, no other code changes should be necessary to get OTP up and running. Mind removing the changes here to Authenticate.tsx and giving it a test?
There was a problem hiding this comment.
Oh woah magic! Okay just updated - appreciate the clarification.
Done! |
Add SMS OTP authentication to the demo app. Tested manually for all new and existing functionalities.