Oracle and DB2 Case Sensitivity Access Control Lists and Content Tracker Reports Secure Mode

Managing Content Tracker 8-57 ■ Custom Reports on page 8-60 ■ External Report Generator on page 8-61 ■ User AuthenticationAuthorization and Auditing on page 8-62 ■ Site Studio Web Site Activity Reporting on page 8-62 ■ Security Checks and Query Results on page 8-63 ■ Using Content Tracker Reports on page 8-69

8.5.1 Oracle and DB2 Case Sensitivity

If Oracle or DB2 is used as the Content Server database, metadata values are case sensitive and care must be used when entering the content metadata values in the applicable query report criteria. As a result, depending on how a value is entered in the corresponding field, Content Tracker Reports may not return all possible matching files. With either an Oracle or DB2 Content Server database, values must be entered exactly as they are entered in the Content Server. Therefore, depending on the lettering structure of the values in the Content Server, the values entered in the query metadata fields will need to be entered in all lowercase letters, all uppercase letters or mixed-case letters. Otherwise, Content Tracker Reports will not return all of the matching files. For example, if the content type in the Oracle or DB2 Content Server database is AdAcc but the user enters it in the query field as adacc, ADACC, or Adacc, Content Tracker Reports will not return any results. In this case, the content type metadata value must be entered using mixed-case letters. This is true for all of the metadata fields in each of the pre-defined query reports.

8.5.2 Access Control Lists and Content Tracker Reports Secure Mode

The security checks preference variable SctrEnableSecurityChecks is set when you install the Content Tracker Reports component. Essentially, this preference variable enables you to select one of two security modes: secure and non-secure. The security checks preference provides the option to employ individual user role and account information to restrict the visibility of content item information in report results. This means that you control what content items and, subsequently, the metadata that users can see in their generated reports. Ideally, users should not be able to see anything through Content Tracker Reports that they couldnt find via a Content Server search. Therefore, if you select the secure mode, the information in any generated report will be filtered based on the users role and account privileges. However, if you have enabled Access Control Lists ACLs on your Content Server instance, the secure mode option in Content Tracker Reports does not work. During installation, you must leave the security checks preference check box blank. This means that on an ACL-based system, the secure mode must be disabled. In this case, it is possible for users other than a system administrator to see information about content items that they would not otherwise be authorized to access and view. Note: For more detailed information about the security checks installation preference and how it will affect the report queries and report results, see Security Checks and Query Results on page 8-63. 8-58 Application Administrators Guide for Content Server

8.5.3 Pre-Defined Reports