| title | ms.custom | ms.date | ms.prod | ms.reviewer | ms.suite | ms.technology | ms.tgt_pltfrm | ms.topic | dev_langs | helpviewer_keywords | ms.assetid | caps.latest.revision | author | ms.author | manager | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Role-Based Security |
03/30/2017 |
.net |
dotnet-standard |
article |
|
|
578cc32b-5654-4d8b-9d8c-ebcbc5c75390 |
13 |
mairaw |
mairaw |
wpickett |
Role-Based Security
Roles are often used in financial or business applications to enforce policy. For example, an application might impose limits on the size of the transaction being processed depending on whether the user making the request is a member of a specified role. Clerks might have authorization to process transactions that are less than a specified threshold, supervisors might have a higher limit, and vice-presidents might have a still higher limit (or no limit at all). Role-based security can also be used when an application requires multiple approvals to complete an action. Such a case might be a purchasing system in which any employee can generate a purchase request, but only a purchasing agent can convert that request into a purchase order that can be sent to a supplier.
.NET Framework role-based security supports authorization by making information about the principal, which is constructed from an associated identity, available to the current thread. The identity (and the principal it helps to define) can be either based on a Windows account or be a custom identity unrelated to a Windows account. .NET Framework applications can make authorization decisions based on the principal's identity or role membership, or both. A role is a named set of principals that have the same privileges with respect to security (such as a teller or a manager). A principal can be a member of one or more roles. Therefore, applications can use role membership to determine whether a principal is authorized to perform a requested action.
To provide ease of use and consistency with code access security, .NET Framework role-based security provides xref:System.Security.Permissions.PrincipalPermission?displayProperty=nameWithType objects that enable the common language runtime to perform authorization in a way that is similar to code access security checks. The xref:System.Security.Permissions.PrincipalPermission class represents the identity or role that the principal must match and is compatible with both declarative and imperative security checks. You can also access a principal's identity information directly and perform role and identity checks in your code when needed.
The .NET Framework provides role-based security support that is flexible and extensible enough to meet the needs of a wide spectrum of applications. You can choose to interoperate with existing authentication infrastructures, such as COM+ 1.0 Services, or to create a custom authentication system. Role-based security is particularly well-suited for use in ASP.NET Web applications, which are processed primarily on the server. However, .NET Framework role-based security can be used on either the client or the server.
Before reading this section, make sure that you understand the material presented in Key Security Concepts.
Related Topics
| Title | Description |
|---|---|
| Principal and Identity Objects | Explains how to set up and manage both Windows and generic identities and principals. |
| Key Security Concepts | Introduces fundamental concepts you must understand before using .NET Framework security. |
Reference
xref:System.Security.Permissions.PrincipalPermission?displayProperty=nameWithType