Security Considerations for Extensions
Every application that targets the common language runtime (CLR) must interact with the CLR security system. When such an application runs, it is automatically evaluated and given a set of permissions by the CLR. Depending on the permissions that the application receives, it either continues running or generates a security exception. The local security settings and policies in the security policy configuration files for a particular report server define the code permissions that an assembly receives.
Before requesting permissions, you need to be aware of the resources and protected operations your extension code is planning to use, and you also need to know which permissions protect those resources and operations. In addition, you need to keep track of any resources accessed by any class library methods that are called by the extension components. For more information, see "Requesting Permissions" in the .NET Framework Developer's Guide.
Extensions deployed to a report server must run as fully trusted, meaning that your extension needs to be part of a code group that is granted the FullTrust permission set. This also means that your extension may have access to certain server resources and operations available through the CLR depending on the user that is being authenticated for a particular report. For more information about code groups and extensions, see Introducing Code Access Security in Reporting Services.
.gif "ms153622.security(en-US,SQL.90).gif") Security Note: |
|---|
| Reporting Services enforces .NET Framework security for all of its extensions. |
The following conditions apply to the deployment of data processing, delivery, rendering, and security extensions in Reporting Services:
- Only the local administrator has permission to deploy an extension.
- Only users with the appropriate read/write permissions can change the configuration files for the Reporting Services component that is being extended.
- Only privileged users have permission to edit the security policy files and enable code access security for an extension.
For more information about code access security in Reporting Services, see Understanding Code Access Security in Reporting Services.
For more information about .NET Framework security, see ".NET Framework Security" in your .NET Framework Developer's Guide.
Initialization of Extension Assemblies
When extensions are first loaded into memory by the report server, they use the service account credentials, because some extension assemblies require specific permissions to access system resources, to read configuration files, and to load other, dependent assemblies. After an assembly has been loaded and initialized, however, all subsequent calls to extension assemblies use the credentials of the user account that is currently logged on.
See Also
Reference
Reporting Services Extension Library