Using custom provider with OTP capabilities #2812
-
Question 💬I'm working on an application that uses Auth0's OTP authentication, the authentication flow is a 3 step process.
I'm working on integrating Next Auth with this flow and I'm stepping on providers at the moment, so far I see that Is possible to implement a provider for my current flow? How to reproduce ☕️This is a question. Contributing 🙌🏽Yes, I am willing to help answer this question in a PR |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Currently, we support only email as an identifier built-in. Are you asking if we could support phone/SMS as well? I have seen people doing it in old issues by customizing the Email provider https://next-auth.js.org/providers/email There is also the RFC #1465 to generalize the Email provider, but nothing has been done yet. |
Beta Was this translation helpful? Give feedback.
Currently, we support only email as an identifier built-in. Are you asking if we could support phone/SMS as well? I have seen people doing it in old issues by customizing the Email provider https://next-auth.js.org/providers/email
There is also the RFC #1465 to generalize the Email provider, but nothing has been done yet.