Configuring security

JReport Designer allows you to allocate security permissions to different principals (users, groups and roles), and thus you can make the view elements in a business view available only for some special principals.

To configure security for a business view, follow the procedure below:

1. Add or import principals.
2. Set the permissions to the view elements of the business view.
3. Save the catalog to save the security configuration.

Adding or importing principals

Before you can configure security for a business view, you first need to define the principals. To do this, in the Business View Editor window, click Tools > Security Configuration to display the Security Configuration dialog. You can either add principals manually or import them from JReport Server. See the dialog.

• To add principals manually,
  1. In the Security Configuration dialog, check the Add Role/Group/User manually option.
  2. In the Role/Group/User tab, click the Add button to add a role/group/user, and give a description for it as required.
  3. Click OK to save the settings.
• To import principals from JReport Server, you must first make sure that JReport Server has been started. Then,
  1. Check Import from JReport Server in the Security Configuration dialog.
  2. Click the Options button, and specify the connection information in the Import from JReport Server dialog, then click OK to connect to the server.
  3. All the principals defined in JReport Server will then be imported, and you can click OK to save them.

Setting permissions

To set permissions to the view elements of a business view,

1. Right-click the view element in the Business View Editor window, and then choose the corresponding item for editing the view element.
2. In the Edit View Element dialog, click the Security tab and set permissions to the element as required. See the dialog.

   

   The Visible permission controls whether a principal can view the business view element in the resource tree of JReport Studio and whether he or she can perform actions based on the element. These actions include inserting and removing. Filtering and sorting are not under security control.

3. Click OK to save the permission settings.

Saving the configuration

When you save the catalog, the permission settings are also saved and they are saved in an authorization file in the same folder as the catalog file. The catalog and authorization files have the same file name but different extensions, for example, if the catalog file is test.cat, the authorization file will be named test.auth. The authorization file is loaded by the view authorization manager of its catalog during runtime.