RE: Multiple Membership providers and AddUserToRole
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Thu, 14 Sep 2006 06:12:53 GMT
Hi MrGrundh,
Nice to hear from you and sorry for the delay response.
As for the System.Web.Security.Roles class you mentioned, it actually call
the Roles.Provider to perform any role management operations. And the
"Provider" property refer to the default RoleProvider configured for the
ASP.NET application. Just like the membership provider, ASP.NET 2.0
configure the SqlRoleProvider as the default role provider. We can also use
the following web.config section to override or define our custom role
providers:
==================
<roleManager defaultProvider="NewAspNetSqlRoleProvider">
<providers>
<add name="NewAspNetSqlRoleProvider"
connectionStringName="LocalSqlServer"
applicationName="MyApplication"
type="System.Web.Security.SqlRoleProvider, System.Web,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</providers>
</roleManager>
=====================
As you can see, the roleprovider also contains a "ApplicationName" which
determine the application in which the role we'll manage.
so for your application, the question here is whether you'll manage the
roles for users in different membership providers(different applications )
together or separate them(each membership application's user will have
their own roles in each application)?
**if you will let those users in different applications share the same
roles, you can just define the single roleProvider or just the default one
and do not need to explicitly set ApplicationName for the role provider.
**if you want each Application has its own roles, you can just define
multiple RoleProviders in the <providers> section above, and then, use the
following code to locate the certain provider according to the
ApplicationName of the certain user:
==========
RoleProvider provider = Roles.Providers["ApplicationName"];
provider.AddUsersToRoles(....)
==========
Hope this helps.
Actually, most of the new services in ASP.NET 2.0 adopt the provider-based
model which is convenient for us to manage them in configuration file.
You can find more info about providers in ASP.NET 2.0 in the following site:
#Provider Toolkit
http://msdn.microsoft.com/asp.net/downloads/providers/default.aspx
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: Multiple Membership providers and AddUserToRole
- From: MrGrundh
- RE: Multiple Membership providers and AddUserToRole
- References:
- RE: Membership.ApplicationName and thread safety.
- From: Steven Cheng[MSFT]
- RE: Membership.ApplicationName and thread safety.
- From: Steven Cheng[MSFT]
- RE: Membership.ApplicationName and thread safety.
- From: Steven Cheng[MSFT]
- RE: Membership.ApplicationName and thread safety.
- From: Steven Cheng[MSFT]
- RE: Membership.ApplicationName and thread safety.
- Prev by Date: Modify .NET Security via code
- Next by Date: Re: Setting impersonation values programmatically
- Previous by thread: RE: Membership.ApplicationName and thread safety.
- Next by thread: RE: Multiple Membership providers and AddUserToRole
- Index(es):
Relevant Pages
|