SqlRolProvider

[dkode]

Hello,

I am trying to select an authentication/role scheme to use for a new
asp.net project. This is the first time I have looked at the new
Membership/Role Providers in ASP.NET 2.0

This project will be housed on a public webhost, so I'm not sure if all
of them support the SqlRoleProvider where asp.net creates its own
tables for the roles/authentication. Also, I will be storing additional
information in the users table such as address,phone, etc... and use
the Users table extensively in my project.

If I am not sure which web host this will be housed at, in addition to
the fact that I will be re-selling this project and don't want to be
attached to a specific webhost, would it be better just to handle the
forms authentication/role management myself?

Thanks for any guidance you can give!

dkode

 

[Erik Funkenbusch]

This project will be housed on a public webhost, so I'm not sure if all
of them support the SqlRoleProvider where asp.net creates its own
tables for the roles/authentication. Also, I will be storing additional
information in the users table such as address,phone, etc... and use
the Users table extensively in my project.

If they support ASP.NET 2.0 and SQL Server, then they support
SqlRoleProvider, and more importantly, SQLMenbershipProvider. It's part of
the framework.

Also, you don't want to alter the aspnet_users table at all. Instead,
create your own users table that uses either the username or userid (GUID)
as the key. This seperates the ASP.NET implementation from yours, and will
make it more robust, especially if MS decides to change the tables in
ASP.NET 2.1 (or whatever they call the next version).

Let the membership system do it's job, managing logins and security. Do
your own stuff in your own tables.

If I am not sure which web host this will be housed at, in addition to
the fact that I will be re-selling this project and don't want to be
attached to a specific webhost, would it be better just to handle the
forms authentication/role management myself?

Only if you need to be ASP.NET 1.1 compatible. The Membership system in
ASP.NET 2.0 is so easy to use, and very robust. It will take you a LOT of
work to duplicate it. Why?