dev-xo
commented
1 year ago Hello @CanRau. First of all thank you for your contribution. Would appreciate if the next time you can open an issue and discuss this with me.
About the request, the Strategy has to be as simple as possible to not introduce leaks into our system. If you need the user email, you can get it from the verify method, that returns email, code, magicLink, form and request.
An example of it:
authenticator.use(
new OTPStrategy(
{
// We've already set up this options.
// ...
},
async ({ email, code, magicLink, form, request }) => {
// Do something with the user email.
// ...
// Get user from database.
let user = await db.user.findFirst({
where: {
email: email,
},
})
if (!user) {
// ...
}
// Return user as Session.
return user
},
),
)Let me know if this is what you was looking for. Closing this for now, I'm here in case you need some help with it.
CanRau
Hey thanks a lot for this fantastic strategy 🙏🏼
As I'm migrating my existing system back over to Remix and improving auth with remix-auth on the way I'd like to have access to the provided email address when storing the code in my db, I have 2 tables, login_session and login_token, and I store the email address in the token table as well, I guess I could update the token in the
sendCodestep, tho I think it'd be nicer to just do it instoreCodeand the code looked straight forward to pass it along as a second argument, this way, instead of providing both in one or sthg, it doesn't break existing implementations.Let me know what you think and/or if I missed anything.
Update: Also got a question, how/where could I best store additional information to redirect the user dynamically back to where they came from?
formin thesendCodeand verify functions seems to be always an empty object{}