Skip to main content

Using Access Control Lists in .Net



Namespace: System.Security.AccessControl

Discretionary Access Control List (DACL) is meant for restricting/granting access to different resources at OS Level to a particular user/group. And Security Access Control Lists (SACL) allows you to audit different resource access permissions.

DACL is collection of Access Control Entries (ACE). RegistryRights, FileSystemRights etc. are the ACE enumerations for their respective resources.

<Type>Security provides the following Method:
(DACL)GetAccessRules,
(SACL)GetAuditRules,
[Add|Remove]AccessRule,
[Add|Remove]AuditRule.

Example:
public static void AddFileSecurity(string fileName, string account,
            FileSystemRights rights, AccessControlType controlType)
{

   // Get a FileSecurity object that represents the
   // current security settings.
   FileSecurity fSecurity = File.GetAccessControl(fileName);
   // Add the FileSystemAccessRule to the security settings.
   fSecurity.AddAccessRule(new FileSystemAccessRule(account,rights, controlType));
   // Set the new access settings.
   File.SetAccessControl(fileName, fSecurity);

}

(DACL)GetAccessRules, (SACL)GetAuditRules return AuthorizationRuleCollection which contain <Type>AccessRule or <Type>AuditRule.



Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...