Re: ASP.NET 2.0 Multiple Membership Providers for Authentication
- From: Brock Allen <ballen@xxxxxxxxxxxxxxxxx>
- Date: Tue, 27 Dec 2005 07:18:16 -0800
You could always write your own provider and delegate to the right one, as necessary.
-Brock DevelopMentor http://staff.develop.com/ballen
Hi,
we are planing two use - if possible - two Membership Providers at the same time for authentication within the same application.
Short background
Imagine a community page, such as a forum. It comes with its very own membership provider given to us by our customer. We cannot change that one. We just have to live with it. Their users are authenticated by this provider and then allowed to use forums, eCards, etc.
Now, they want us to add a backend to their site. For that we need another membership provider which will determine whether the user has the rights needed to administer/change/add/delete certain pages/content areas. As both - totally different user roles - need to work on the same pages, we need a solution to implement two different authentication schemes in the same application at the same time.
Is there a way to accomplish that and where would we start?
Thanks in advance, Daniel
.
- Follow-Ups:
- References:
- Prev by Date: Re: Basic theory question about the ASP.NET Machine account
- Next by Date: Multiple Users with impersonation using one account
- Previous by thread: ASP.NET 2.0 Multiple Membership Providers for Authentication
- Next by thread: Re: ASP.NET 2.0 Multiple Membership Providers for Authentication
- Index(es):
Relevant Pages
|