Report Permissions Properties

If this flag is activated, the current cache will be cleared on the next request. The flag is deactivated afterwards. All cached reports up to now will be generated on the next request.

Default value: false

With this option, the report location is activated, meaning that only reports (*.rpt files) from specified sources and subfolders are accepted.

Default value: true

The report location is a list of sources where reports can be found, ready to be run by the server. All other report sources are then deactivated for security reasons. A source can be a folder, including its subfolder, e.g. C:Reports or a URL such as http://www.webserver.com/reports/.

To add a new source, this source must be entered into the text field. For file sources, the folder button can be clicked to search through the file system. After entering the new source, it can be added to the report location by clicking the Add button. Note: The source must exist and be valid, otherwise it can not be added to the report location list. In order to remove an entry from the report location list, the entry must be selected and deleted via the Delete button.

Warning: The deactivation of the report location feature can be a security threat if you have reports not meant for public viewing, therefore it should only be deactivated in a safe area like an intranet.

With this option, all reports on file system locations can be executed. File system locations are e.g. local hard drives, removable media or shared directories.

Default value: true

With this option, all reports accessed using the JNDI protocol can be executed.

Default value: true

Please note: Repository is a feature exclusive to i-net Clear Reports Plus. Therefore a Plus license is required.

With this option, all reports accessed using the Repository protocol (repo:) can be executed.

Default value: true

With this option, all reports on localhost locations can be executed. Localhost locations are e.g. LOCALHOST, 127.0.0.1 and the local IP address.

Default value: true

With this option, the access permission controls are activated, allowing only specified groups and users to open reports for which they have the permissions.
If the check is enabled and no access permissions are specified then report execution is prohibited for all users. Also the permissions are additive, which means that a right is granted to the current user if it is granted to the current user itself, or to user "*" (all users), or to a special group, where current user belongs to.

Default value: false

Access Permissions - Stored in Configuration

These access permissions are given to all report files matching the specified pattern, e.g. *.rpt. It does not matter in which directory the reports are located. A pattern can contain characters, the asterisk symbol (*) as a wildcard for any number of symbols, the question mark (?) as a wildcard for a single symbol and/or slashes (/) as folder separators.
For example you can give the access permission to all reports in all folders with the pattern *.rpt to all users in the admin group, which means this admin permission is for any file with the rpt ending in any path.

These access permissions are used only if the configuration (in which the permissions have been set) is active.

Access Permissions - Stored in Folder

These access permissions are specific to the folder they were created for. With these permissions you can control the access of report files included in the same folder in that the permissions are stored. For example, you could enable all users (*) to access the specific report overview.rpt or a certain group financial to access all financial reports with the file pattern *financial.rpt.
If the permissions are copied into another folder then the access permissions are specific to this folder, as well.
These access permissions are independent of which i-net Clear Reports configuration is active.

In order to create or modify access permissions for a folder or URL, you must enter the path to the folder or the URL in the text field or use the Browse button to select the folder. If access permissions already existing for the selected folder or URL, they will be loaded automatically. It is also possible to load the access permissions through a URL (http or ftp), but the permissions file can not directly be stored on the web server, so it is necessary to store it locally. This permissions file must then be manually copied onto the web server. It is also possible to search for existing access permissions by clicking the Search button. This opens a dialog box which shows the folders containing access permissions. The search starts with the given path and searches all sub-folders.

Access Permissions: Creating and Editing

With the Add Pattern button, a new pattern can be created with matches one or more reports. For the patterns, the asterisk symbol (*) is used as a placeholder for any number of characters, so all reports with the ending .rpt are matched with the pattern *.rpt, all reports beginning with the letter a are matched by a*.rpt and all reports containing the word admin are matched by *admin*.rpt.
The question mark (?) is used as placeholder for a single symbol. Slashes (/) are allowed for patterns used in Access Permissions - Stored in Configuration, only. Note that for these permissions, slashes are also covered by the wildcard character, so *admin*.rpt would also enable access to any report in any subfolder of any folder with "admin" anywhere in the name or path.

Once a pattern has been added, users and groups can be added to this pattern, or all groups and users can be specified using the pattern *

The patterns in the list, the groups, and the users can be changed with the Edit button or deleted with the Remove button.