[authentication] custom sign up using react
Hey folks. I was following along this page https://docs.kinde.com/authenticate/custom-configurations/custom-authentication-pages/ because I am trying to add a custom
sign-up and sign-in screens. However, I do not quite understand the steps to call sign-in login function with user email and password, and I also do not understand or see how registration can be done with a custom sign-up screen.
In short, I want to have my own sign-up/sign-in forms in react, to ensure the form experience and error handling is the same across the entire application.Kinde docs
Custom sign-up and sign-in pages
Our developer tools provide everything you need to get started with Kinde.
3 Replies
Would it be possible using a backend as a proxy somehow? Using the Java SDK
We understand that passwordless is arguably more secure and a great commodity. However, the users we are targetting are not the most tech savy and are often a bit aged. So they are more used to the
email + pwd model.
Not really. It's B2B. We are creating restaurant management software with more contemporary features and friendlier ui/ux. Existing alternatives were written at least 20 years ago. I've used them in the past. 😛
We will use social on the mobile app, when we eventually get there, but that would the B2C part.Hi @Francisco "Klogan" Barros ,
The only way we support authenticating users is via our hosted routes. You can bring your own initial view where you can take in the email, plus handle any other logic you wish to carry out on the initial view.
To provide a secure flow all passwords, MFA etc are handled on Kinde hosted screens. You can bring your own custom domain to these screens so will not leave your brand domain.
In the next couple of months we will be releasing an updated customisation feature where you will be able to bring richer customisation to the hosted view.
This approach is really suited also for a B2B business when customers have stricter auth requirements will enable you to handle them with ease with no or minimal code changes.
Alright Dan. Thank you. For the time being, I believe we are going with passwordless. For the amount of subscribers we will have in the start and given they will be working in close colaboration with us, it should not be an issue. 🙂
Following this one: https://www.youtube.com/watch?v=63IT5qlXJ64 😊 (but for react spa)