Help on PrincipalPermission Demand Throwing Exception

[PrincipalPermission(SecurityAction.Demand, Name=@"MYDomain\MyUserName")]
static void TestMethod()
{
Console.WriteLine("Test Message");
}

public static void Main(string[] args)
{
WindowsIdentity wID = WindowsIdentity.GetCurrent();
Console.WriteLine("Current User: {0}", wID .Name);

try
{
TestMethod();
}
catch (System.Security.SecurityException ex)
{
Console.WriteLine("Exception: {0}", ex.Message);
}

Console.Read();
}

Abba Biya

Shoud add the following line for it to work.

AppDomain.CurrentDomain.SetPrincipalPolicy(Princip alPolicy.WindowsPrincipal);


some observations:

Security Principals listed on separate demands will be OR whereas if listed
all in one SecurityAction.Demand, it will be AND.

[PrincipalPermission(SecurityActioin.Demand, Authenticated = true, Role =
@"CONTOSO\Admins")]
will allow only authenticated and users from Admins group.

If we change it to the following:
[PrincipalPermission(SecurityActioin.Demand, Authenticated = true)]
[PrincipalPermission(SecurityAction.Demand, Role = @"CONTOSO\Admins")]

Authenticated users with out being Admins will be able to run this code.
this is a Logical OR.

This is great.



"Abba Biya" wrote:

> [PrincipalPermission(SecurityAction.Demand, Name=@"MYDomain\MyUserName")]
> static void TestMethod()
> {
> Console.WriteLine("Test Message");
> }
>
> public static void Main(string[] args)
> {
> WindowsIdentity wID = WindowsIdentity.GetCurrent();
> Console.WriteLine("Current User: {0}", wID .Name);
>
> try
> {
> TestMethod();
> }
> catch (System.Security.SecurityException ex)
> {
> Console.WriteLine("Exception: {0}", ex.Message);
> }
>
> Console.Read();
> }
>

Abba Biya