Harden MS Reporting Services Using Custom Extensions, Part 2

In Part 1, you learned to create a custom security model for Microsoft Reporting Services. Now, tighten the screws by adding role membership authentication and stave off problems by troubleshooting and debugging your custom extensions ahead of time.

by Teo Lachev

February 1, 2005

n Part 1 of this series, you learned that, by default, the Report Server uses Windows-based security to authenticate and authorize incoming requests based on the Windows identity of the interactive user. While Windows-based security works well for intranet applications, it is usually impractical for Internet-facing applications. This leaves you with two implementation choices.

It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com.
Already a member?

To become a member of DevX.com create your Member Profile by completing the form below.
Membership is free!

Already registered? Sign In

E-mail (User Name)

Create a Password

Re-enter Password

First Name

Last Name

Company

Company Size

Address

City

State/Province

Country

Postal Code/Zip

Job Function

Phone

Note: Extension number is optional, but may be included by adding an "x" before the extension number.

By registering you will also be signed up for the Enterprise Development Daily newsletter.
After registering you may choose to opt-out by clicking on the "Manage Profile" link.

Cancel

Harden MS Reporting Services Using Custom Extensions, Part 2

In Part 1, you learned to create a custom security model for Microsoft Reporting Services. Now, tighten the screws by adding role membership authentication and stave off problems by troubleshooting and debugging your custom extensions ahead of time.

Whitepapers and eBooks

Webcasts

Downloads and eKits

Tutorials and Demos