Re: Architecture: Custom Profile Provider with Active Directory Membership
- From: Steven Nagy <learndotnet@xxxxxxxxxxx>
- Date: Mon, 13 Aug 2007 20:43:17 -0700
Hi Nicholas,
We want to use AD for authentication because it means the users don't
need "another username/password".
Also our product does not have a user maintenance section for
application users. We rely purely on sys admin maintaining AD users in
the standard way. Our product essentially leaves "zero footprint" in
this regard. So user administration is not a concern.
The only alternative then as I see it is to write a custom profile
provider base from scratch.
Or at least reflect Microsofts and fix it.
I guess this even shows a fault in the concept of the Provider
pattern; once you have an interface to a provider, you really are
locked in there.
Thanks heaps.
Steven
.
- Follow-Ups:
- Re: Architecture: Custom Profile Provider with Active Directory Membership
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Architecture: Custom Profile Provider with Active Directory Membership
- References:
- Architecture: Custom Profile Provider with Active Directory Membership
- From: Steven Nagy
- Re: Architecture: Custom Profile Provider with Active Directory Membership
- From: Nicholas Paldino [.NET/C# MVP]
- Architecture: Custom Profile Provider with Active Directory Membership
- Prev by Date: Re: Architecture: Custom Profile Provider with Active Directory Membership
- Next by Date: Re: How often do you use "delegates" (Events) over "interfaces" anyway?
- Previous by thread: Re: Architecture: Custom Profile Provider with Active Directory Membership
- Next by thread: Re: Architecture: Custom Profile Provider with Active Directory Membership
- Index(es):
Relevant Pages
|