Wasp/OpenSaas newbie here. I've privacy conscious users and want to show I'm taking steps to protect stored personally identifiable information. This means encrypting their login email address in the DB.
Is there a way to do this by injecting custom logic/overriding functions in the right places in the email auth provider so I'm not covering the same ground? Or am I going to have to write a whole auth flow to do what I want?
I'd like users to still able to easily request a password reset and stuff, which is why I don't want to swap to the username auth. I think the overall approach should work because any time we need to email the user, they're inputting their email address anyway.
Recent Announcements
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.