サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.2 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing 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
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using Windows PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Column dependencies for setting values

There may be dependencies between individual values, for example, by using value templates or customizers that require values to be set in a specific order. In the case of One Identity Manager tools the correct order is enforced through blocking or releasing input fields. In the case of data import and when using web service interfaces, the correct order for setting values also has to be ensured.

The following data sources assume the following sequence for specifying the order for setting values:

  1. Customizer

    The dependencies between columns and an object are stored in customizers.

  2. Custom defined dependencies

    To define custom dependencies between columns

    1. In the Schema Editor, select a table column.

    2. In the Column properties view on the Dependencies tab, define the predecessor of this column.

  3. Column dependencies due to value templates

    In this case, values used by a template (for example, Person.Firstname, Person.Lastname) are set before values that are created by a template (for example, Person.CentralAccount).

If circular dependencies occur whilst determining the order for setting the values, they are stopped at the point of lowest priority.

Related topics

Permitted column values

To only allow a specific value in a column, you can define a list with the permitted values. This list of permitted value is resolved once the column's display value has been formatted. For some columns of the One Identity Manager schema, already permitted values are supplied when the schema is installed.

NOTE: You can only enter or extend a list of permitted values for a column if the option Customizing permitted values list is not allowed is not set.

To create a list of permitted values

  1. In the Designer, select the One Identity Manager Schema category.

  2. Select the table and start the Schema Editor with the Show table definition task.

  3. Select the column and then the Column properties view.

  4. Select the Value settings tab and enable the Defined list of values option.

  5. Click and enter the following properties.

    • Value: Value for the value list (technical name).

    • Display value: Name used to display the value. Translate the given text using the ... button.

    • Sort: Sort order of displaying the values in the list.

    • Disabled: Specifies whether the value is disabled.

    NOTE: To edit a value, select the value and click . To delete a value, select the value and click . To delete all values, click .

  6. Select the Database > Commit to database and click Save.

IMPORTANT: Compile the database to bring the list of permitted values into effect.

Example:

In the Spare field no. 01 input field for an identity, the values internal and external should be permitted. The list of permitted values is defined as followed:

1=internal 2=external

For an identity with the value 1, the display value internal is shown on the forms in the Manager.

Display columns with permitted values in the Manager

A special control element is used in the Manager to display columns for which a list of permitted values has been defined. The control element is displayed as a simple input field if no list is defined. If a list is defined the control element is shown as a menu.

Figure 10: Input field for list of defined values (with and without defined entries)

The control element is only available for columns on default predefined forms as well as custom columns (usually CustomProperty01-CustomProperty10).

Related topics

Specifying requirements for MVP columns

Values in multi-values property (MVP) columns are delimited by char(7) or chr(7). Specify other requirements for each value of the MVP column.

To specify requirements for a MVP column

  1. In the Designer, select One Identity Manager Schema.

  2. Select the table and start the Schema Editor with the Show table definition task.

  3. Select the column and then the Column properties view.

  4. Select the Value settings tab and set the Multi-value column option.

  5. In the Multi-value specification menu, configure the following settings.

    • Unique: Set this option if the value must be unique.

    • Case sensitive: Set this option if the case sensitivity should be taken into account when the value is tested.

    • Accent insensitive: Set this option if accent characters should not be taken into account when the value is tested.

  6. Select the Database > Commit to database and click Save.

Related topics

Defining bitmasks

You can only define bitmasks for columns with theint type.

NOTE: You can only enter or extend a bitmask for a column if the option Customizing bitmasks is not allowed is not set.

To create a bitmask

  1. In the Designer, select One Identity Manager Schema.

  2. Select the table and start the Schema Editor with the Show table definition task.

  3. Select the column and then the Column properties view.

  4. Select the Value settings tab and set the Defined bitmask option.

  5. Under Sort criteria of bitmask, select the sort criteria for displaying the value.

    You have the following options:

    • Bit position: Sort by position.

    • Display: Sort by display value.

  6. Click and enter the following properties.

    • Bit position: Each bit position. The first bit in the definition start with the index 0.

    • Display value: Name used to display the value. Translate the given text using the ... button.

    • Disabled: Specifies whether the value is disabled.

    NOTE: To edit a value, select the value and click . To delete a value, select the value and click . To delete all values, click .

  7. Select the Database > Commit to database and click Save.

Related topics
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択