User1954717099 posted
I'm building an application using the new ASP.NET 5 framework and am familiarizing myself by playing around with the default template.
In said template, which I thought had implemented user authentication pretty well, there is an Account Controller and a Manage Controller. The Account Controller handles user account creation, as well as the login and logout functionality of the site. The
Manager Controller handles basic user account management, such as changing a user password or support for adding two factor authentication.
Although I see the reasoning behind this design choice to some extent, I want to design the routing for my site in a particular way, and would need to combine the two controllers to accomplish this. I did this on the template, and everything continued working
fine.
Aside from the one controller being arguably too large, are there any issues with doing this? Are there security risks that I am overlooking? Do you know why Microsoft made this design choice when building a basic Identity user authentication template?
Thanks for your response.
