Introduction to Microsoft SQL Server Reporting Services 2005 - Professional SQL Server 2005 Reporting Services - page 38

Windows. The client needed a way to ensure secure access to reports. We created a custom security exten-
sion that used their existing code to allow user access. By extending the security infrastructure, we were
able to leverage all of Reporting Services' features.
Rendering Extensions
The final extension type is the rendering extension. Say that you had a requirement to deliver reports in
a Rich Text Formatting (RTF) format. You could use the standard rendering interfaces to create the next
extension. Once the extension was created, it would be available for every report, even those reports that
have been archived as snapshots. Creating rendering extensions is not a trivial task. You must account
for all of the different report elements and how they will be displayed. However, it does open the door
for third-party companies to extend the Reporting Services infrastructure.
Scripting
Most report management and delivery features may be automated through a simple scripting interface.
A single utility executable, rs.exe , is used to obtain access to the vast capabilities of the Report Services
Web service. You can create scripts to manage batch processing of reports or programmatically manipu-
late any exposed functionality of reporting service. Capabilities are similar to that of the Web service
proxy used in .NET programming code, but a scripting solution is a simpler approach that doesn't
require complex programming or a compiled project. Scripting is an ideal approach for system adminis-
trators to create simple maintenance, deployment, and ad hoc delivery solutions.
Subscriptions
Subscriptions enable users to request reports to be delivered to them automatically. Based on a schedule
(single-instance or recurring) reports may be delivered using any available deliver extension (e-mail, file,
or custom) in any available rendering format. Subscriptions can be either standard, where a user requests
the scheduled delivery of a specific report, or data-driven, where a group of users can request the sched-
uled delivery of one or more reports. This is an extremely powerful tool that can be used to provide
report content in an efficient manner to users in practically any location or work schedule. Chapter 10
will lead you through this compelling feature.
Securing Reports
Reporting Services uses a role-based security model that is installed and configured by default. This model
is highly extensible and may be changed after installation to use a custom authentication component.
In order for sensitive data to be protected from intrusion, it should be encrypted both at the Report Server
and in the web browser or client application. The preferred method to do this is to use Reporting Services'
built-in support for certification-based encryption over the Secure Sockets Layer (SSL) . Implementing SSL
will automatically redirect web requests to an address at the same location using the https:// prefix. This
enables bidirectional encrypted streaming of all data over port 443 (by default) rather than the standard
HTTP port 80. Reporting Services supports levels of automatic encryption, which are detailed in the section