Using Role-Based Security
Microsoft® SQL Server™ 2000 Reporting Services uses role-based authorization and Windows Authentication to determine who can perform operations and access items on a report server.
Role-based authorization categorizes into roles the set of actions that a user can perform. Examples of roles that are useful on a report server include Content Manager, Publisher, and Browser.
All users interact with a report server within the context of a role. A user can have multiple roles, and the operations that are supported by a role determine the actions that a user can perform. Roles can vary across users and for different items. For example, a user who is a member of the Content Manager role for one report may be a member of the Browser role for another report.
To ensure that your report server is secure from the start, Reporting Services provides default security through a set of predefined roles that are assigned to built-in Windows accounts. Default security consists of role assignments that grant access to local administrators. You must create additional role assignments to make the report server accessible to other user and group accounts. For instructions, see Server Deployment Checklist.
To work with role-based security, use Report Manager.
This section describes the Reporting Services security model, the default security implementation, and how to add more role assignments. The following table describes the topics in this section.
|Reporting Services Security Model||Introduces the Reporting Services security model and describes key components.|
|Using Default Security||Describes the preset role assignments and role definitions that control access to a report server.|
|Configuring Security Through Role Assignments||Explains how to configure security and provides best practices for customizing security.|