How do I configure security for AppManager reports? (NETIQKB41497)

How do I configure security for AppManager reports?

To configure security for AppManager reports, you can set various permissions for accounts within your networking environment.  In addition, Microsoft IIS configuration and Windows NT security settings are required to restrict access.

Controlling access to the AMReports virtual directory

You can limit access to AppManager reports by defining the authentication methods necessary to access the AMReports virtual directory via the default IIS Web site.  The following instructions assume a default installation of the Web management server and the report agent on a single computer.

To define authentication methods for the AMReports virtual directory on a Microsoft Windows 2000 computer:

1. Click Start | Programs | Administrative Tools | Internet Services Manager.
2. Expand the server object (computer name).
3. Expand the Default Web Site object.
4. Right-click AMReports, then click Properties.
5. Click the Directory Security tab.
6. Under 'Anonymous access and authentication control', click Edit.
7. Select an authentication method (Note:  You are permitted to choose all methods): 
   
   

   Select	To
   Allow Anonymous access	Permit access to anyone
   Basic authentication	Prompt users for a user name and password.
   Digest authentication for Windows	Prompts users for a user name and domain servers password, but sends a hash value rather than a password. Used with IIS 5.0.
   Integrated Windows	Authenticate users based on the Authentication security tokens associated with the Windows accounts under which the Web browsers are running.

   
   
8. Click OK.
9. Click OK.

To define authentication methods for the AMReports virtual directory on a Microsoft Windows NT computer:

1. Click Start | Programs | Windows NT 4.0 Option Pack | Microsoft Internet Information Server | Internet Services Manager.
2. Expand the Internet Information Server folder.
3. Expand the server object (computer name).
4. Expand the Default Web Site object.
5. Right-click AMReports, then click Properties.
6. Click the Directory Security tab.
7. Under Anonymous Access and Authentication Control, click Edit
8. Select an authentication method (Note:  You are permitted to choose one, two, or all three methods):
   
   

   Select	To
   Allow Anonymous Access	Permit access to anyone
   Basic Authentication	Prompt users for a user name and password.
   Windows NT Challenge/Response	Authenticate users based on . the security tokens associated with the Windows accounts under which the Web browsers are running.

    
9. Click OK.
10. Click OK.

 

Controlling access to reports by setting folder permissions

You can further restrict access to reports by creating additional folders within the Report folder, setting permissions for those folders based on the intended audience, and then writing reports in the appropriate folders.  For example, create one folder for account managers and one folder for IT personnel, and set permissions for those folders that restrict access based on group membership.

By restricting access to reports in this manner, you can ensure that each intended audience sees exactly the reports it needs, and is spared sifting through material of no concern. When a user from one of those groups connects to AMReports via the URL, only the reports in the folder available to that account are visible.

Note:  Consult your Microsoft Windows documentation for information about account management and setting permissions for folders.

Writing reports to existing folders

After you have created the necessary additional folders within the Report folder, you can then write reports directly to those folders.

To write reports to a specific folder:

1. Start a Report Script job.
2. Click the Values tab of the Properties dialog box.
3. In the Select output folder parameter, click the Browse [...] button.
4. Select specific name of folder.
5. In the Folder field, type the path to the output folder.

Formerly known as NETIQKB41497

Additional information on this topic can be obtained from pages 86-90 of the AppManager Reporting Guide.