Use attributes on your classes and/or methods. You need something like
this:
[PrincipalPermissionAttribute(SecurityAction:
emand,
Authenticated=True,
Role="Progdir")]
The Visual Studio help puts it like this:
_______________________________________________________________________________________
PrincipalPermissionAttribute can be used to declaratively demand that
users running your code belong to a specified role or have been
authenticated. Use of Unrestricted creates a PrincipalPermission with
Authenticated set to true and Name and Role set to a null reference
(Nothing in Visual Basic).
The scope of the declaration that is allowed depends on the SecurityAction
that is used. PrincipalPermissionAttribute cannot be applied at the
assembly level.
The security information declared by a security attribute is stored in the
metadata of the attribute target and is accessed by the system at run
time. Security attributes are used only for declarative security. For
imperative security, use the corresponding permission class.
Important Prior to a demand for principal permission it is necessary to
set the current application domain's principal policy to the enumeration
value WindowsPrincipal. By default, the principal policy is set to
UnauthenticatedPrincipal. If you do not set the principal policy to
WindowsPrincipal, a demand for principal permission will fail. The
following code should be executed before the principal permission is
demanded:
AppDomain.CurrentDomain.SetPrincipalPolicy(PrincipalPolicy.WindowsPrincipal).
Example
The following example demonstrates how PrincipalPermission can be used
declaratively to demand that the current user is Bob and belongs to the
Supervisor role.
Visual Basic Copy Code
<PrincipalPermissionAttribute(SecurityAction.Demand, _
Name := "Bob", Role := "Supervisor")> Public Class SampleClass
C# Copy Code
[PrincipalPermissionAttribute(SecurityAction.Demand, Name="Bob",
Role="Supervisor")]
C++ Copy Code
[PrincipalPermissionAttribute(SecurityAction:
emand,Name="Bob",
Role="Supervisor")]
J# Copy Code
/** @attribute PrincipalPermissionAttribute(SecurityAction.Demand,
Name = "Bob", Role = "Supervisor")
*/
The following example demonstrates how to demand that the current user's
identity is Bob, regardless of role membership.
Visual Basic Copy Code
<PrincipalPermissionAttribute(SecurityAction.Demand, _
Name := "Bob")> Public Class SampleClass
C# Copy Code
[PrincipalPermissionAttribute(SecurityAction.Demand, Name="Bob")]
C++ Copy Code
[PrincipalPermissionAttribute(SecurityAction:
emand,Name="Bob")]
J# Copy Code
/** @attribute PrincipalPermissionAttribute(SecurityAction.Demand, Name =
"Bob")
*/
The following example demonstrates how to demand only that the user is
authenticated.
Visual Basic Copy Code
<PrincipalPermissionAttribute(SecurityAction.Demand, _
Authenticated := True)> Public Class SampleClass
C# Copy Code
[PrincipalPermissionAttribute(SecurityAction.Demand, Authenticated=true)]
______________________________________________________________________________________
HTH
Peter
shapper said:
Hello,
How to I check if a user is authenticated and if it is what is its
role?
I am using Asp.Net 2.0 and forms authentication.
Thanks,
Miguel
