Re: Off loading the providers
- From: Dominick Baier <dbaier@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Aug 2006 16:32:09 +0000 (UTC)
You have to write a Web Service or Service Component and a membership/role provider that communicates with them. Thats quite some work. Classes like MembershipUser have to be restructured to be marshalable via XmlSerializer e.g.
---
Dominick Baier, DevelopMentor
http://www.leastprivilege.com
Anyone have a good idea how to make the membership, role and profile
providers be remote and be accessed only using http/soap so that I
don't have to have LDAP, msldap and SQL traffic from my web server to
the middle tier/back end?
I looked at using a web service or enterprise services but in either
case I have to inherit from Webservice or ServicedComponent which to
me means it can not then be typed as a MembershipProvider or one of
the other providers.
.
- Follow-Ups:
- Re: Off loading the providers
- From: MikeS
- Re: Off loading the providers
- References:
- Off loading the providers
- From: MikeS
- Off loading the providers
- Prev by Date: Off loading the providers
- Next by Date: Re: how to use 'aspnet_Membership_CreateUser' directly through T-SQL
- Previous by thread: Off loading the providers
- Next by thread: Re: Off loading the providers
- Index(es):