A way to avoid deriving from the provider classes in mvc authentication
Posted
by
Shymep
on Stack Overflow
See other posts from Stack Overflow
or by Shymep
Published on 2011-11-30T17:33:35Z
Indexed on
2011/11/30
17:50 UTC
Read the original article
Hit count: 311
Looking for the best practice for authentication in MVC I unfortunately didn't find the clear answer to my question. Thinking of the problem I tried to imagine some priciples that could be useful in my design. Well,
- I would like to use a base AccountController class
- I want to place all the tables such as "Users", Roles, Rights etc into my own database. But I wouldn't like to implement the standard aspnetdb design (which can be easy got by using aspnet_regsql)
So the main question is can I do this without deriving abstract classes like MembershipProvider, RoleProvider etc? What I would prefer not to do is implement all the abstract methods from these classes.
The second question is still about the best practice for authentication e.g. for the small projects, for the large ones?
© Stack Overflow or respective owner
