This documentation is archived and is not being maintained.

SiteIdentityPermissionAttribute Class

Allows security actions for SiteIdentityPermission to be applied to code using declarative security. This class cannot be inherited.

For a list of all members of this type, see SiteIdentityPermissionAttribute Members.


[Visual Basic]
<AttributeUsage(AttributeTargets.Assembly Or AttributeTargets.Class _
   Or AttributeTargets.Struct Or AttributeTargets.Constructor Or _
NotInheritable Public Class SiteIdentityPermissionAttribute
   Inherits CodeAccessSecurityAttribute
[AttributeUsage(AttributeTargets.Assembly | AttributeTargets.Class
   | AttributeTargets.Struct | AttributeTargets.Constructor |
public sealed class SiteIdentityPermissionAttribute :
[AttributeUsage(AttributeTargets::Assembly |
   AttributeTargets::Class | AttributeTargets::Struct |
   AttributeTargets::Constructor | AttributeTargets::Method)]
public __gc __sealed class SiteIdentityPermissionAttribute :
   public CodeAccessSecurityAttribute
   AttributeUsage(AttributeTargets.Assembly | AttributeTargets.Class |
   AttributeTargets.Struct | AttributeTargets.Constructor |
class SiteIdentityPermissionAttribute extends

Thread Safety

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.


Site identity is only defined for code from URLs with the protocols of HTTP, HTTPS, and FTP. A site is the string between the "//" after the protocol of a URL and the following "/", if present, for example, in the URL This excludes port numbers. If a given URL is, the site is, not

Sites can be matched exactly, or by a wildcard ("*") prefix at the dot delimiter. For example, the site name string * matches as well as Without a wildcard, the site name must be a precise match. The site name string * will match any site, but will not match code that has no site evidence.

The scope of the declaration that is allowed depends on the SecurityAction that is used.

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.


[Visual Basic, C#, C++] The following example of a declarative attribute shows the correct way to request SiteIdentityPermission and states that you must have at least this permission to run your code. Code will only execute if it is run from the Web site

[Visual Basic] 
<Assembly: SiteIdentityPermissionAttribute(SecurityAction.RequestMinimum, _
Site := "")>
'In Visual Basic, you must specify that you are using the assembly scope when making a request.

//In C#, you must specify that you are using the assembly scope when
// making a request.

//In C++, you must specify that you are using the assembly scope when
// making a request.

[Visual Basic, C#, C++] The following example shows how to demand that the calling code has SiteIdentityPermission at link time. Code will only execute if it is run from the Web site

[Visual Basic] 
<SiteIdentityPermissionAttribute(SecurityAction.Demand, _
 Site := "")> Public Class SampleClass



[JScript] No example is available for JScript. To view a Visual Basic, C#, or C++ example, click the Language Filter button Language Filter in the upper-left corner of the page.


Namespace: System.Security.Permissions

Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family

Assembly: Mscorlib (in Mscorlib.dll)

See Also

SiteIdentityPermissionAttribute Members | System.Security.Permissions Namespace | Extending Metadata Using Attributes | SiteIdentityPermission | Site | SiteMembershipCondition