Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Identity Manager 8.1.5 - Compliance Rules Administration Guide

Compliance rules and identity audit
One Identity Manager users for identity audit Basic data for setting up rules Setting up a rule base rule check Creating custom mail templates for notifications
Mitigating controls Configuration parameters for Identity Audit

Extended property master data

Enter the following data for an extended property.

Table 7: Extended property master data
Property Description

Extended property name

Name of the extended property.

Property group

The property group for structuring extended properties. You can assign a primary property group to a property on the master data form. Extended properties are grouped by this property group in navigation.

If an extended property needs to be assigned to several property groups, then you can use the Assign property groups task to assign additional property groups.

Lower scope boundary

Lower scope boundary for further subdivision.

Upper scope boundary

Upper scope boundary for further subdivision.

Description

Text field for additional explanation.

Spare field no. 01 ... Spare field no. 10

Additional company-specific information. Use the Designer to customize display names, formats, and templates for the input fields.

Detailed information about this topic

Specifying scoped boundaries

You can subdivide extended properties by specifying scoped boundaries. You are not obliged to enter scoped boundaries. If you do enter a lower boundary you are not required to enter an upper one. However, if you specify an upper boundary, you have to enter a lower one.

Take note of the following when defining scoped boundaries:

  • Basically, any string is permitted as a lower or upper scoped boundary.
  • You can use * as a wildcard for any number of characters (even null).
  • Wild cards can only be added to the end of a string, for example, AB*. Strings such as *AB or A*B are not allowed, for example.
  • If you enter a lower boundary without a wildcard, you cannot use a wildcard in the upper boundary.

The following restrictions apply for the length of the string:

  • If you enter a lower and upper boundary without a wildcard, the strings have to be the same length, for example, lower boundary 123/upper boundary 456. A lower boundary of 123 and an upper of 45, for example, is not permitted or a lower boundary 123/upper boundary 4567 is also not allowed.
  • If you use a wildcard in the lower boundary but none in the upper boundary, then the length of the upper boundary string needs to be the same as or bigger than the string in the lower boundary.
  • If you use a wildcard in the lower and upper boundary, they have to be the same length, for example, lower boundary 123*/upper boundary 456*. A lower boundary of 123* and an upper of 45*, for example, is not permitted or a lower boundary 123*/upper boundary 4567* is also not allowed.

Additional tasks for extended properties

After you have entered the master data, you can run the following tasks.

Extended property overview

Use this task to obtain an overview of the most important information about an extended property. For this you need to take into account the affiliation of the extended property to the different One Identity Manager objects.

To obtain an overview of an extended property

  1. In the Manager, select the Identity Audit | Basic configuration data | Extended properties | <property group> category.

  2. Select the extended property in the result list.

  3. Select the Extended property overview task.

To obtain an overview of a property group

  1. In the Manager, select the Identity Audit | Basic configuration data | Extended properties category.

  2. Select a property group in the result list.

  3. Select the Property group overview task.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation