Re: GenericPrincipal
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Sep 2007 16:21:23 -0500
I think if you want to use your existing user database, you would need to
create your own custom membership provider that talks to your SQL server.
The default one doesn't necessarily require SQL express, but it does assume
a specific schema that certainly won't match your existing database.
I would think this would be pretty doable though. The source code for the
SQL membership provider is freely available for you to look at and modify.
It is probably a better way to go than by starting with the lower level
forms auth as you'll get a lot more integration that way.
You might also consider migrating your existing user store to the schema
expected by the SQL membership provider.
I'm not really an expert in the SQL membership provider stuff (I'm a
directory guy and think you should put users in directories like AD and ADAM
:)), so if you have more specific questions about the SQL stuff, you'd need
to ask someone else.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"WhiskeyRomeo" <WhiskeyRomeo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FDF52BAD-D3FE-4994-9A61-D7D6F9057047@xxxxxxxxxxxxxxxx
I am new to VS2005 and .NetFramework 2.0. But if you use the built in
authentication of a website, doesn't that create a SQL Express database to
maintain membership logins, passwords, and roles?
Is there a way to use the membership provider without the overhead of
creating a duplicate database when you have all the information in a SQL
Server 2000 database? See my later post (Forms Auth Roles being ignored).
WR
"Joe Kaplan" wrote:
.
- References:
- GenericPrincipal
- From: Erick
- Re: GenericPrincipal
- From: Joe Kaplan
- GenericPrincipal
- Prev by Date: Role Provider Security Trimming Issue
- Next by Date: Re: Session parameter lost memory
- Previous by thread: Re: GenericPrincipal
- Next by thread: RE: Trust level required for AppDomain.CurrentDomain.UnhandledExcept
- Index(es):
Relevant Pages
|