e-mail confirmation at register & forgotten password

[nschurmann]

Sup guys, is there a configuration to make the registration process to validate the email first? The use case is basically so the users don't start registering emails that are not of their property, this could lead to users impersonating other persons.

[remicastaing]

A configuration to confirm the email address at registration is not yet available. But some people are working on it.

[nschurmann]

Those are good news, thanks for the reply remicastaing.

[JaKXz]

Has the latest version of nodemailer been considered? @remicastaing could you show me where the work is happening? 😄

[remicastaing]

I was considering nodemailer and email-templates. There you can find my WIP. It is not the generator and I hadn't yet time to catch up with the latest commit of the canary branch.

[kingcody]

@JaKXz, I also have a decent amount of work done on this. I actually implemented it in most of my projects that use fullstack. @remicastaing and I have been discussing the options available so far. I've mainly been waiting for a few other PRs to get into canary before I or Rémi, for that matter, made a PR. Not trying to speak for Rémi, I just know there were some other additions in the pipe that would simplify the implementation, ex. some of chester1000's work.

[JaKXz]

Oh okay, cool! I was just curious @kingcody, thanks for clearing that up.

[thomporter]

Something kinda related to this is a "Forgot Password" feature. I was looking into the idea of adding it, but I found this thread and thought maybe it should be part of the same PR, or at least, come after it so as to use the same email template system & mailer. I would love to help with this any way I can. I'm trying to get a "minimal set of features" added to this project so it's "ready for production"! I freakin' love this generator. =)

[JaKXz]

Good point @thomporter, I would love to see that as well. Let's use this issue to address both these things -- I'm looking forward to the PR.

[remicastaing]

Here, you will find an attend to implement the two features with JWT (a nice idea from @kingcody). Please, clone, test and give some feedback.
Both features work, but there is still work to be done (error catching, tests, etc.).
Don't forget to change local.env.sample.jsto local.env.js and add some credentials to the email service. I used gunmail but node-mailer allows a lot of other supported mail services.

[kingcody]

@remicastaing does node-mailer not fit your needs? Or was it just easier for you to use mailgun?

[remicastaing]

I use node-mailer. Mailgun is just a mail service, like gmail, yahoo, etc...

[kingcody]

I see, my apologies :) thought you were saying mailgun had a module like node-mailer.

Do you think it would be good to leverage the HTTP1.1 verbs in your routes? It would allow you to shorten them to something like:

router.get('/mail', auth.isAuthenticated(), controller.sendMailAdressConfirmationMail);
router.post('/mail', controller.confirmMailAddress);
router.get('/password', controller.sendPwdResetMail);
router.post('/password', controller.confirmResetedPassword);

Just a thought...

[remicastaing]

Or something like that:

router.get('/mailconfirmation', auth.isAuthenticated(), controller.sendMailAdressConfirmationMail);
router.post('/mailconfirmation', controller.confirmMailAddress);
router.get('/passwordreset', controller.sendPwdResetMail);
router.post('/passwordreset', controller.confirmResetedPassword);

In the end, we're no getting or posting a mail.