Managing Security in VS .NET

Creation QR-Code in VS .NET Managing Security

9

Manage jobs Manager Report Server properties Manage Report Server security Manage roles Manage shared schedules View Report Server properties View shared schedules

In this procedure, you will assign the AWSalesAnalyst group to a new role based on the System User role with permission to view shared schedules only.

Open Report Manager in Internet Explorer at http://localhost /Reports. Click the Site Settings link at the top right corner of the Home page. Anyone with system role assignment that includes View Report Server Properties or Manage Report Server Properties will have the Site Settings link on any page in Report Manager. Click the Configure Site-Wide Security link.

Reporting Services has two default system roles that you can use unchanged or extend to better meet your needs. The System User role, by default, allows access to the Site Settings page so that role members can view the server properties and shared schedules. Any user who needs to use a shared schedule for executing scheduled reports or creating subscriptions must be assigned to this role. The default tasks for the System Administrator role include not only managing server properties and shared schedules (which can be viewed and edited), but also managing running jobs, system role assignments, and role definitions.

The System Role Assignments page is displayed:

Notice the default system role assignment of the local system administrators group, BUILTIN\Administrators, as System Administrator. You will always need at least one System Administrator role assignment. Click the New Role Assignment button on the Report Manager toolbar. The New System Role Assignment page is displayed:

9

As with item-level role assignments, you can assign a user or group to multiple roles. If you click the Role check box above the list of roles, you can select all roles. You can also add another role by clicking the New Role button, or edit the existing roles by clicking the role link. Click the System User link. Click the Copy button. A new role is created with the same tasks that are assigned to the System User role. Type a name for the new role: Shared Schedule User. Add a description that details the assigned tasks: View shared schedules.

Tip By listing the tasks in the description, a System Administrator won t have to open the role definition to see the task assignments in the New System Role Assignment page.

Clear the View Report Server Properties check box. Your screen should look like this:

Tip You can also add a new system role or edit an existing system role whenever necessary by using the Site Settings link at the top of any Report Manager page. Click the Configure System-Level Role Definitions link to access the System Roles page. 10 Click the OK button.

11 In the Group Or User Name box, type AWSalesAnalyst. 12 Select the Shared Schedule User link check box.

Your screen looks like this:

The System Role Assignments page is displayed:

9

Now the AWSalesAnalyst role can use shared schedules with the reports that it can access as defined by item-level role assignments.

Sometimes different users need access to the same report, but each user is allowed to see only some of the data. For example, a sales territory manager might be allowed to view only data that pertains to his or her sales territory. In this case, using item-level security works only if you create a separate report using a different query in each report to restrict the data to a single sales territory. If many reports require a similar separation for different groups of users, the administrative overhead of maintaining and securing all the variations can quickly become overwhelming. Instead, you can choose a technique that leverages the use of one report, yet still satisfies the requirement to restrict data by user.

The simplest way to restrict the data that a user can see in a report is to use linked reports with parameters. Using this approach, you can easily control which data is displayed in the report, and then use item-level security to control access to each linked report. Alternatively, you can design a report that takes advantage of the User function from the global parameters collection to identify the current user. You can pass the user identification either to a query parameter or to a filter to restrict the data in the report.