Search code examples
asp.netmembership

Advantage of implementing my own role based authorization instead of using Membership?

I read this article here http://www.codeproject.com/KB/web-security/RolesFormsAuthorization.aspx

What is the limitation of Membership that would require me to implement my own ?

Solution

  • The primary limitation is using the arbitrary database design of the Membership provider along with being relegated to the Membership API.

    I have always found the membership provider API to be kludgy (at best) and the database design it requires to work out of box to be atrocious. I have never once used the builtin membership to fruition ... I think ever but absolutely not in any application I have in production.

    So to sum it up, the primary reason to not use the membership provider out of box is the database design will not match your design and you will have a hell of a time trying to use your application database + membership database together or you will have a large amount of insidious data duplication of users, ASP.NET user vs application user.