Help hooking into 2.0 membership w/existing users, roles

[dw]

Hello -

We have an existing ASP.NET 1.0 web site that already has a set of tables
for Users (user id and password plus many other attributes), Roles, etc.

We are trying to migrate to ASP.NET 2.0 and we're hoping to hook into or
extend the memberhsip and security features that are part of the 2.0 feature
set.

Is this possible? And, if so, is it a difficult process? Are there any
links or articles on how to accomplish this? I have searched around and have
found some the explain how to extend the 2.0 stuff...but not with an
already/existing database of users and roles.

thanks for any help.
- will

 

[PeterKellner]

Hello -

We have an existing ASP.NET 1.0 web site that already has a set of tables
for Users (user id and password plus many other attributes), Roles, etc.

We are trying to migrate to ASP.NET 2.0 and we're hoping to hook into or
extend the memberhsip and security features that are part of the 2.0
feature
set.

Is this possible? And, if so, is it a difficult process? Are there any
links or articles on how to accomplish this? I have searched around and
have
found some the explain how to extend the 2.0 stuff...but not with an
already/existing database of users and roles.

thanks for any help.
- will

I'm assuming you are using sqlserver? Probably, the easiest thing to do
would be to take the source to the Membership Provider Microsoft has so
generously made availabe and modify it to access your tables instead. For
my own purposes, I have a simple Membership Provider that I use that doesn't
have all the bells and whistles microsoft provides.

Good luck.

 

[dw]

Yes, we're using SQL 2005. What we don't want to do, if possible, is to have
to maintain two sets of User and UserRoles tables. We already have those
tables in place and working with our asp.net 1.1 web site. Modifying the MS
Membership Provider sounds like the right way to go, though I would be
concerned about future updates from MS that we might not be able to implement
because we have modified to use our own.

Guess we'll see.

Thanks for the feedback.
- will

 

[PeterKellner]

I think you are OK with future updates as long as you role your own
provider. They may add functionality, but I don't believe they will break
anything existing. (but then again, I'm not the betting type).

Good luck.

 

[Dominick Baier [DevelopMentor]]

always ask yourself why you want to do that. It seems you have a working
solution already - what do you gain from forcing this solution into the provider
pattern??

don't just do providers for providers sake -

and btw - the login controls can also be used without a provider.

 

[dw]

I agree...but I have a boss that wants to force this new solution....so I
don't have a choice. I am trying to reduce the potential risk and find an
easy way to support the new providers.