Does SuperTokens have a way to obfuscate the password sent from the frontend? Looking at the Next.js example, the password just seems to be submitted as is. Seems a little risky.
06/12/2022, 12:38 PM
Yea! Absolutely. You can override the sign in / sign up recipe function on the frontend to hash it before calling the original implementation. This would send the hashed password to the backend. And the backend would further hash it in the core before saving it
One down side of this is that you can’t reliably enforce password syntax rules. Cause the backend no longer gets the original password. Whilst the frontend can check for password syntax before having it, it can be easily hacked by changing the frontend code
06/12/2022, 12:45 PM
Ah, interesting. That does make sense. Okay. Thanks for the helpful info!