Administrators can create dynamic security policies for catalogs published to the server using security files. The security files contain catalog internal security definitions and are generated in JReport Designer (for details, see Exporting catalog security into a security file in the JReport Designer User's Guide).
With dynamic security, administrators can dynamically change the security policy applied to a catalog.
To create a dynamic security policy, take the following steps:
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, click the false link in the Is Default column for the dynamic security.
If you want to remove a dynamic security policy, check it in the dynamic security table, then click the Delete link above the table. You can delete multiple dynamic security policies at a time.
The security file based on which the dynamic security policy of a catalog is created can be modified. To do this, click the Upload link in the Controls column for the dynamic security, then in the Upload Dynamic Security dialog, select another security file to create the dynamic security for the catalog.
The dynamic security defined on server can be downloaded to a file. To do this, click the Download link in the Controls column for the dynamic security, in the displayed dialog, click OK to save it. You can then further modify the security definitions in the file according to the format of DynamicSecurity.xsd, which is in <install_root>\help\samples\DynamicSecurity
. After editing, you can upload the file to a dynamic security policy to change the security definitions in the policy.
When a catalog is specified with a default dynamic security policy, when running reports, dashboards, or Visual Analysis templates which use the catalog, no matter interactive, on-demand, or scheduled, JReport 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.
If the security file mentions a business view/business cube/report cube element, but the element is not in the catalog, it will be ignored.
If there is no default dynamic security specified for a catalog, the security definitions created in the catalog at design time will be used.