Use attributes on your classes and/or methods. You need something like
this:
[PrincipalPermis sionAttribute(S ecurityAction:: Demand,
Authenticated=T rue,
Role="Progdir")]
The Visual Studio help puts it like this:
_______________ _______________ _______________ _______________ _______________ ____________
PrincipalPermis sionAttribute 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 PrincipalPermis sion 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. PrincipalPermis sionAttribute 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 WindowsPrincipa l. By default, the principal policy is set to
Unauthenticated Principal. If you do not set the principal policy to
WindowsPrincipa l, a demand for principal permission will fail. The following
code should be executed before the principal permission is demanded:
AppDomain.Curre ntDomain.SetPri ncipalPolicy(Pr incipalPolicy.W indowsPrincipal ).
Example
The following example demonstrates how PrincipalPermis sion can be used
declaratively to demand that the current user is Bob and belongs to the
Supervisor role.
Visual Basic Copy Code
<PrincipalPermi ssionAttribute( SecurityAction. Demand, _
Name := "Bob", Role := "Supervisor")Pu blic Class SampleClass
C# Copy Code
[PrincipalPermis sionAttribute(S ecurityAction.D emand, Name="Bob",
Role="Superviso r")]
C++ Copy Code
[PrincipalPermis sionAttribute(S ecurityAction:: Demand,Name="Bo b",
Role="Superviso r")]
J# Copy Code
/** @attribute PrincipalPermis sionAttribute(S ecurityAction.D emand,
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
<PrincipalPermi ssionAttribute( SecurityAction. Demand, _
Name := "Bob")Publi c Class SampleClass
C# Copy Code
[PrincipalPermis sionAttribute(S ecurityAction.D emand, Name="Bob")]
C++ Copy Code
[PrincipalPermis sionAttribute(S ecurityAction:: Demand,Name="Bo b")]
J# Copy Code
/** @attribute PrincipalPermis sionAttribute(S ecurityAction.D emand, Name =
"Bob")
*/
The following example demonstrates how to demand only that the user is
authenticated.
Visual Basic Copy Code
<PrincipalPermi ssionAttribute( SecurityAction. Demand, _
Authenticated := True)Public Class SampleClass
C# Copy Code
[PrincipalPermis sionAttribute(S ecurityAction.D emand, Authenticated=t rue)]
_______________ _______________ _______________ _______________ _______________ ___________
HTH
Peter
"shapper" <md*****@gmail. comwrote in message
news:11******** **************@ 16g2000cwy.goog legroups.com...
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
