Learn about configuring security for RtReports

While RtReports allows you to configure permissions access for various user types, it does not depend on the Data Archive server, which contains the RtReports data to administer these permissions.

Rather, all requests from RtReports users to the Data Archive server containing RtReports data are channeled through a single PI trust connection (defined as List of access permissions for RtReports Server (to Data Archive)). For versions 3.1.1 and earlier, this PI trust must have read/write access to the Module Database, as well as read access to the point database on the Data Archive server. For version 3.2, the trust must also have read/write access to the point database to store report properties in tag annotations.

In addition, the RtReports Server accesses the Data Archive server when generating a report. This access is read-only to both the point and module databases.

Most PI access via the RtReports Editor is accomplished via web service calls to the RtReports Server trusted connection described above. However, the Editor also has its own read-only connection to the Data Archive server defined when running test reports (defined as "RtReports Editor" above). This Data Archive server is the one defined by the currently-tested report template.