Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in 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 Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Example of cross-object value templates

If a value template references a value from another object, it can be accessed using the FK relation.

Figure 11: Effect of Cross Object Value Templates

If, for example, the surname of an Active Directory user account (ADSAccount.Surname) is derived from the surname of an employee (Person.Lastname), enter the template for the column ADSAccount.Surname as follows:

Value = $FK(UID_Person),Person.Lastname$

If the employee’s surname changes, the last name of the Active Directory user changes, too. The column Person.Lastname is therefore the sender and the column ADSAccount.Surname is the receiver. The relation is mapped in the table DialogNotification as follows:

Person.Lastname --> ADSAccount.Surname

Formatting of values

You can customize the column formats to your requirements and create your own additional formats. You can also use predefined formatting scripts along side formatting types to check values in a column.

Note: You can get an overview of the existing columns in the system with predefined formatting types or formatting scripts in Designer in One Identity Manager Schema | Formatting rules.

Related Topics

Defining unique columns

If there is a column or column combination for a table that needs to be unique, you define multicolumn uniqueness in Designer. The columns are collected into a unique groups.

Example
  • For the Hardware table, you must ensure that the name of the hardware is unique. For the Hardware table, a Hardware unique group with the Ident_Hardewarelist column is created.
  • For the ADSDomain table, the combination of the domain identifier and its defined name must provide unique values. For the ADSDomain table, an ADSDomain unique group with the Ident_Domain and DistinguishedName columns are created.

To group together columns in a unique group

  1. In Designer, select One Identity Manager schema.
  2. Select the table and start the Schema Editor with the task Show table definition.
  3. In the Table properties view, select the Multicolumn uniqueness tab and click .

  4. Enter the following information.

    Table 27: Table properties for multicolumn uniqueness

    Property

    Description

    Unique group

    Name of the unique group of columns.

    Columns

    Enable the columns that must be unique when combined.

    Ignore empty values

    Specifies whether empty values are permitted in a unique group. If all the columns in one group are empty, group uniqueness cannot be tested. If this option is not set, empty values are permitted but only once for each column.

    NOTE: To prevent empty values, define a minimum column length in the column definition.

    Related Topics

Limiting the column length

You can use the column definition to control the length of the values to be entered. For example, the login name of an Active Directory user account is limited to a maximum of 20 characters. You can also use the column definition to define which columns are required columns.

To define the length of a column

  1. In the One Identity Manager, select Designer Schema.
  2. Select the table and start the Schema Editor with the task Show table definition.
  3. Select the column and then the Column properties view.
  4. Select the Value calculation tab and edit the following properties.

    • Max. length: Enter the maximum length of the column. If the value is equal to 0, the length is taken from the database schema.
    • Min. length: Enter the minimum length of the column. Columns with a minimum length of 1 or greater are flagged as required fields in the front-ends.
Related Topics
Related Documents