Open dubesar opened 3 years ago
When it comes to passwordless authentication, we need to understand that the process deviates from the traditional registration/login procedure. In this paradigm, your email provider acts as the source of authentication.
Here's a brief overview:
In this workflow, the token essentially functions as your password.
If a user logs out and needs to log back in, the same process is followed:
This process generates a new token each time a user needs to log in, enhancing security by not requiring a persistent password that can be compromised.
Remember, in passwordless authentication, the token is your "password". This token is ephemeral and changes with every login attempt, which is the principle behind the security of passwordless authentication.
I hope this clarifies the concept for you. Let me know if you have any further questions.
how do i view this tokens via the shell?
I'm trynna implement this with sessions since I'm using templates
I have registered and the user logs out from client app, now how to login with same emailid and create new token? Is there a way to do so?