Previous TopicNext Topic

Dynamic Security

Logi Report Server administrators can create dynamic security policies for catalogs published to the server using security files, which contain catalog internal security definitions. With dynamic security, administrators can change the security policy applied to a catalog at run time, without having to edit the security in Logi Report Designer and publish the catalog again.

Developer users can also use API to manage dynamic security.

Select the following links to view the topics:

• Creating Security Files
• Creating Dynamic Security
• Changing the Security File of a Dynamic Security Policy
• Downloading Dynamic Security
• Applying Dynamic Security

Creating Security Files

The security files that can be used to create dynamic security on Logi Report Server are in XML format. You can create the security files by yourself, however the best way to generate a security file is using Logi Report Designer.

A security file can contain security definitions of Record Level Security (RLS), Column Level Security (CLS) and Business View Security. For how to define RLS and CLS in an XML file, refer to Importing/Exporting Security Information from/to External XML Files in the Logi Report Designer Guide. As for the format of business view security, you can refer to the sample file DynamicSecurity.xml, which is stored in <install_root>\help\samples\DynamicSecurity.

Suppose that a business view security policy is defined as follows:

In the XML file, it will be written like below:

When the Allowed Set and Denied Set are defined using expressions, for example:

In the XML file, the business view security policy will be like this:

Creating Dynamic Security

To create a dynamic security policy, take the following steps:

1. In the Logi Report Server console, point to Administration on the system toolbar, and then select Security > Dynamic Security from the drop-down menu to display the Dynamic Security page.

   

2. Select New Dynamic Security on the task bar.
3. In the New Dynamic Security dialog box, select the Browse button next to the Catalog text box.
4. In the Select Catalog dialog box, browse to the catalog you want to create dynamic security for and select OK.
5. Select the Browse button next to the Security File text box, select the security file based on which the dynamic security for the catalog will be created, then select Open.
6. Select OK in the dialog box to create the dynamic security, and it is added to the dynamic security table.
   

One catalog can have several dynamic security policies. In this case, you can specify which one of them will be used as the default dynamic security of the catalog. To do this, select the false link in the Is Default column for the dynamic security.

If you want to remove a dynamic security policy, select it in the dynamic security table, then select the Delete link above the table. You can delete multiple dynamic security policies at a time.

The following are details about the options in the Dynamic Security page:

Changing the Security File of a Dynamic Security Policy

The security file based on which the dynamic security policy of a catalog is created can be modified. To do this, select the Upload link in the Controls column for the dynamic security, then in the Upload Dynamic Security dialog box, select another security file to create the dynamic security for the catalog.

Downloading Dynamic Security

The dynamic security defined on server can be downloaded to a file. To do this, select the Download link in the Controls column for the dynamic security, in the displayed dialog box, select OK to save it. You can then further modify the security definitions in the file. After editing, you can upload the file to a dynamic security policy to change the security definitions in the policy.

Applying Dynamic Security

When a catalog is specified with a default dynamic security policy, when running reports, dashboards, or analysis templates which use the catalog, no matter interactive, on-demand, or scheduled, Logi Report will always try to load the dynamic security for the catalog before running and try to use the security defined in the security file on which the dynamic security is created to replace the catalog security.

• For business view
  For each given principal and business view, if there is security definition in the security file, the whole security definition for this principal on this business view will be replaced.

  If the security file mentions a business view element, but the element is not in the catalog, it will be ignored.

• For security entry
  For a given principal and a security entry, if there is CLS definition in the security file, it will replace the CLS in the catalog security. If there is RLS definition in the file, it will replace the RLS in the catalog security.

If there is no default dynamic security specified for a catalog, the security definitions created in the catalog at design time will be used.

Previous TopicNext Topic