The solution proposed by Tadit Dash is good, but that is the simplest way. The problem with it is, that you mix a "helper" that should serve on or more of your applications with your application logic. In general that is not the place and the means to do this.
In VS you have two templates, one uses windows authentication (actually IIS is doing it), the other has compact SQL database as backend to store the role and membership information. These are the keywords if you want a complete custom solution: you need to
implement a membership provider[
^] and a
role provider[
^]. At this level a Microsoft MVC application is just a n ASP.NET application.
You can go further, like presented in this article:
Custom MembershipProvider and RoleProvider Implementations that use Web Services[
^]
Submit an article or tip