Creating Secure Report Queries Using an External Report Generator

Managing Content Tracker 8-73 Content Tracker Reports is successfully updated with the new setting and is effective immediately. You do not need to restart Content Server.

8.5.9.8 EnablingDisabling Security Checks for Report Queries

If the security checks preference variable is enabled, and a secure version of a query exists in the contenttrackerreports_query.htm file, then Content Tracker Reports will use the secure query to generate the requested report. However, you may decide that certain reports do not need to be generated using security checks. Accordingly, you can selectively disable the secure version of any report query. To disable security checks account matching for particular report queries:

1. In a text editor, open the contenttrackerreports_query.htm file:

IntradocDircustomContentTrackerReportsresourcescontenttrackerreports_ query.htm

2. Locate the secure version of the query that you want to disable.

3. Rename the query. For example, if you want to disable the qSctrUsersByType_SEC

query, you can add the suffix _disabled to the query name: qSctrUsersByType_SEC_disabled Renaming the query ensures that the Content Tracker Reports service can not find the secure query in the contenttrackerreports_query.htm file. Instead, the non-secure version qSctrUsersByType will be used.

4. Save and close the contenttrackerreports_query.htm file.

5. Restart the Content Server to apply the changes.

8.5.9.9 Creating Secure Report Queries

For most of the pre-defined report queries, there are both non-secure and secure versions in the contenttrackerreports_query.htm file. Optionally, you can create a secure version for any query that does not currently have one. In particular, this includes any non-secure custom queries that you have added. To create a secure version of a non-secure report query: 1. In a text editor, open the contenttrackerreports_query.htm file: IntradocDircustomContentTrackerReportsresourcescontenttrackerreports_ query.htm 2. Locate the query for which you want to create a secure version. For consistency, you should add your secure query immediately following the corresponding non-secure version. 3. Design your secure SQL report query: It might be helpful to review Step 2 in the procedure for Creating Custom Report Queries on page 8-70. Note: Renaming a secure query is a temporary disabling solution. Later, if you decide that you prefer to use the secure version of a query, you can easily re-enable it by restoring its original name. Alternatively, you can delete the secure version of the query. However, if you subsequently reconsider, you would need to recreate the entire secure version of the query. 8-74 Application Administrators Guide for Content Server 4. Adjust your query to ensure that it follows the pattern of the existing secure queries: a. In the FROM clause, include the Revisions table. b. In the WHERE clause, include the SCTR_SECURITY_CLAUSE token. This acts as a placeholder for the WHERE clause that the Content Tracker Reports service inserts. c. Complete the query following the established pattern in the existing secure queries. The Figure 8–4 illustrates a typical report query pairing. 5. Save and close the contenttrackerreports_query.htm file. 6. Restart the Content Server to apply the changes. Figure 8–4 Examples of Non-Secure and Secure Report Query Versions

8.5.9.10 Using an External Report Generator

To generate custom reports from an external reporting tool:

1. Open the external reporting tool application