Improve User Registration With Verify/Confirm Email Flow With ASP.NET Core Identity and Web API

[@CodeMaze]

Thank you all for watching and for your support. ►► If you want to check out all our courses you can do that here: courses.code-maze.com/courses/

[@10Totti]

Good tutorial thanks!

[@CodeMaze]

You're welcome!

[@GabyLangis]

awesome video!! is there a way to add time to the email token ? in my testing i forgot 2 times to confirm the email and when on doing something else when i came back to confirm the email 1 hour later the token was expired this is why i was wondering...

[@CodeMaze]

Hi. Yes there is a way. Please check the: "Modifying Lifespan of the Email Token" section of my article: code-maze.com/email-confirmation-aspnet-core-identity/

[@GabyLangis]

@@CodeMaze Thanks man you are the best!! x)

[@prmep476]

What you have in your custom class Message ?

[@CodeMaze]

It is the part of the Email Service project. Just properties like (To, Subject, Content...) and some other stuff. Nothing too related to the confirm/verify implementation.

[@AhmedAlkurdi7]

@@CodeMaze can you show us the code in class Message Please

[@kakhachaduneli5296]

Hello, first of all thanks. Some part of the code is added here, which you did not record in the previous registration and authorization videos. :(

[@CodeMaze]

Hi. You are very welcome. Any specific part you are pointing at? As far as I remember, everything needed for this functionality to be implemented is recorded.

[@kakhachaduneli5296]

@@CodeMaze Here is an example: I could not see where this record was : await _userManager.AddToRoleAsync(user, "Visitor");

[@CodeMaze]

I see, but it really doesn't affect any functionality from this video. It is just assigning the role to the user, nothing more.

[@kristiadhy]

I've tried this, but I got an error on the verification. I've checked and checked again between the token generated and the token when confirmed, and they're identical. I'm still not sure what's going on.

[@kristiadhy]

I've finally figured it out! The issue was that I mapped the DTO to the model first and then executed the CreateAsync method. Then, before I sent the email confirmation, I did the mapping again, which caused the user model that created the token was different.

[@CodeMaze]

I am glad you resolved the issue. You can always use the source code, if you are patreon member. It can help greatly.