|RoleManagerModule||This module ensures that roles will be assigned to the currently logged-on user for every request. It attaches to the Application_AuthenticateRequest event and creates an instance of RolePrincipal containing the roles the user is assigned to automatically if the roles API is enabled in web.config.|
|RoleProvider||Base class for every roles provider that defines the interface you must implement for a custom RoleProvider. Every custom provider must be inherited from this class.|
|RoleProviderCollection||A collection of roles providers. This collection allows you to iterate through the configured roles providers on your system and for your application, which is handy when writing an administration application or pages for your application.|
|SqlRoleProvider||Implementation of a roles provider for SQL Server-based databases.|
Gets role information for an authenticated Windows user based on Windows group associations.
|AuthorizationStoreRoleProvider||Implementation of a roles provider for storing roles in an Authorization Manager-based store. Authorization Manager ships with Windows Server 2003 and allows you to declaratively define application roles and permissions for this role. Your application can use Authorization Manager for programmatically authorizing users.|
|Roles||You use the Roles class as your primary interface to the roles store. This class includes methods for programmatically managing roles.|
This is a IPrincipal implementation that connects the configured roles with the authenticated user. It is created automatically by the RoleManagerModule if the roles API is enabled.
If you are going to use Role-based authorization in your ASP.NET project you can find more information from the article How to use Roles API for Role-Based Authorization in ASP.NET, and you can use some of the classes which are listed in the next table: