Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the One Identity Manager Extending the Launchpad Task Definitions for the User Interface Applications for Configuring the User Interface Icons and Images for Configuring the User Interface Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

Data Retrieval using an SQL Query

Data queries with the query module "SQL" are executed directly on the database without checking user access permissions. This means that a column to be used in the report is displayed even though the user may not have access permission to it.

Table 294: Data Source SQL Properties
Property Meaning
Name Name of the data source.
Description Description of data source.
Query module Select the query module "SQL".
Query

Full database query SQL syntax. The query must contain all the columns used in the report. You can also use SQL parameters in the query. Add these parameters subsequently to the report by entering them on the tab Parameters.

Example:

The query should return the employees (table Person) assigned to an department. The department (UID_Department) is found with the object key (XObjectKey). This is passed as a parameter to the report. The employee‘s first name (firstname), last name (lastname) and department name (departmentname) are queried.

Select Firstname, Lastname, Departmentname

from person join Department

on person.uid_Department = department.uid_Department

where Department.XObjectKey = @ObjectKeyBase

Related Topics

Data Retrieval using a Database View

You can use query module "View" to create data queries using predefined database views and in this way control user access rights.

Table 295: Data Source View Properties
Property Meaning
Name Name of the data source.
Description Description of data source.
Query module Select the query module "View".
View name Name of the database view.
Condition Condition for limiting the data set returned from the database table. You formulate the condition as a valid WHERE clause for database queries. You may use SQL parameters in the condition. Add these parameters subsequently to the report by entering them on the tab Parameters.
Sort by The data queries are sorted by these database view columns.
Related Topics

Data Retrieval using an Object

Data queries with the query module "Object" are created using the object layer and therefore take user access permissions fully into account.

Table 296: Data Source Object Properties
Property Meaning
Name Name of the data source.
Description Description of data source.
Query module Select the query module "Object".
Parent query In a parent query, restrictions are applied to the data record that are passed on to subsequent queries, all members of a department, for example. Parameters that are defined in the parent query are also available in subsequent queries.
Table Select the table to find the object in.
Columns

Columns to use in the report.

Some columns are always added to the report definition and must not be explicitly entered here. These include:

  • The table's primary key column.
  • All columns used in the table display template.
  • "Dummy" columns (_Display and _DisplayLong) supplied by the table's display template.
  • An additional column (<column>_Display) is also created for the display value for foreign key columns and columns with a list of defined values or multi language entries.
Resolve foreign key Set this option if the display value of the referenced object should be returned in <column>_Display rather than the UID.
Condition

Condition for limiting the data set returned from the table. You formulate the condition as a valid WHERE clause for database queries. You may use SQL parameters in the condition. Add these parameters subsequently to the report by entering them on the tab Parameters.

Columns in a parent query are formatted with the following syntax:

@<parent query name>.<parent query column>

Sort by The data queries are sorted by these table columns.
Related Topics

Data Retrieval using Single Object History

Use data queries with the query module "Single object history" when you want to create reports about a single object, for example, one employee, with its history data.

Table 297: Properties of Data Source Single Object History
Property Meaning
Name Name of the data source.
Description Description of data source.
Query module Select the query module "Single object history".
Parent query In a parent query, restrictions are applied to the data record that are passed on to subsequent queries, all members of a department, for example. Parameters that are defined in the parent query are also available in subsequent queries.
Object key

The object key can be queried directly or using a parameter. Add these parameters subsequently to the report by entering them on the tab Parameters. Columns in a parent query are formatted with the following syntax:

<parent query name>.<parent query column>

Min. date or time period

Use the minimum date to specify the point in time that the history data should start from. You can define the date directly or using a parameter. In the case of a parameter, the minimum date of all the effected entries in the history database are found. Add these parameters subsequently to the report by entering them on the tab Parameters.

Resolve foreign key Set this option if the display value of the referenced object should be returned rather than the UID.

The data query returns the following columns.

Table 298: Columns from a Data Query using Single Object History
Column Meaning
ChangeID Unique identifier (UID) for the record.
ObjectKey Object key or the record.
ObjectUID Unique identifier (UID) for the modified objects.
User Name of user that caused the change.
ChangeTime Time of change
ChangeType Type of change (Insert, Update, Delete).
Columnname Name of column whose value has changed.
ColumnDisplay Display name of column whose value has changed
OldValue Old column value.
OldValueDisplay Old column display value. Only if the option Resolve foreign key is set.
NewValue New column value.
NewValueDisplay New value display value. Only if the option Resolve foreign key is set.
Related Topics
Related Documents