Chat now with support
Chat with Support

Identity Manager 8.1 - Identity Management Base Module Administration Guide

Basics for Mapping Company Structures in One Identity Manager Managing Departments, Cost Centers and Locations Working with Dynamic Roles Employee administration
One Identity Manager users for employee administration Basic data for employee master data Entering employee master data Employee's central user account Employee's central password Employee's default email address Mapping multiple employee identities Disabling and deleting employees Password policies for employees Limited access to One Identity Manager Assigning company resources to employees Displaying the origin of an employee's roles and entitlements Analyzing role memberships and employee assignments Additional tasks for managing employees Determining an employee‘s language Determining an employee's working hours Employee reports
Managing Devices and Workdesks Managing Resources Set up Extended Properties Appendix: Configuration parameters for managing departments, cost centers, and locations Appendix: Configuration parameters for managing employees Appendix: Configuration Parameters for Managing Devices and Workdesks

Calculating Inheritance through Hierarchical Roles

Employees, devices and workdesks can only be members in roles that are extensions of the BaseTree table. These role are display in views, each of which represents a certain of the table BaseTree. The One Identity Manager data model contains the following views:

Table 2: BaseTree table views
View Meaning

Department

Graphical representation of departments

Locality

Graphical representation of locations

PROFITCENTER

Graphical representation of cost centers

AERole

Application Role Mapping

NOTE: Because the views are subsets of the table BaseTree, all the inheritance mechanisms described below also apply to the views.

Inheritance comes from the table BaseTree. The BaseTree table can map any number of hierarchical role structures using the UID_Org - UID_ParentOrg relationship. These are stored in the table BaseTreeCollection. All the roles inherited from the given role are listed and, depending on their subset of the table BaseTree there is a corresponding, so-called *Collection table containing a subset of the role hierarchy.

The following relations apply in the table BaseTreeCollection:

  • UID_Org is the role that inherits.
  • UID_ParentOrg is the role that passes down inheritance.

This principle also applies to bottom-up trees that pass inheritance from bottom to top, even if the parent relationship from the BaseTree table appears to be reversed.

Each role inherits from itself.

Each role in a role hierarchy must be related to the table OrgRoot ("Role classes"). OrgRoot is the anchor for role hierarchies. A role hierarchy is always mapped for one role class only. Roles from different role classes may not be in one and the same role hierarchical or point to each other through a parent-child relationship.

Figure 11: Visual of a Hierarchical Role Structure based on an OrgCollection

A role inherits everything that is assigned to its parents in the role hierarchy including those it assigned to itself. If the number of roles from which the role has inherited something changes, the assigned objects are recalculated for all members of this role. If the number of assigned objects of one class changes, the objects assigned in this class are recalculated for all members of the role. If an application is assigned to a parent application, the members of the table BaseTreeHasApp are recalculated.

The members of a role inherit all assignments that belong to them according to the BaseTree and also previous structures according to BaseTreeCollection through primary and secondary role structures.

Calculation of Assignments

When inheritance is calculated, an entry is made for each assignment in the corresponding assignment table. Each table, in which assignments are mapped, has a column XOrigin. The origin of an assignment is stored in this column as a bit field. Each time an entry is made in the assignment table, the bit position is changed according to the assignment type. Each assignment type changes only its allocated bit position.

That means:

  • Bit 0: direct assignment.
  • Bit 1: indirect assignment but not through a dynamic role.
  • Bit 2: assignment through a dynamic role.
  • Bit 3: assignment through an assignment request.
  • Bit 4: module specific bit. For detailed information, see the administration guide of the module in which the bit is used.

XIsInEffect shows whether an assignment is in effect. For example, if an employee is disabled, marked for deletion, or classified as a security risk, inheritance of company resources can be prohibited for this employee. The group assignment is maintained but the assignment has no effect.

DBQueue Processor monitors changes to the XOrigin column. The column XIsInEffect is recalculated when changes are made to the value in XOrigin.

Table 3: Possible values for column XOrigin

Bit 3

Bit 2

Bit 1

Bit 0

Value in XOrigin Meaning
0 0 0 1 1 Only directly assigned.
0 0 1 0 2 Only indirectly assigned.
0 0 1 1 3 Directly and indirectly assigned.
0 1 0 0 4 Assigned through dynamic roles.
0 1 0 1 5 Assigned directly and through dynamic roles.
0 1 1 0 6 Assigned indirectly and through dynamic roles.
0 1 1 1 7 Assigned directly, indirectly and through dynamic roles.
1 0 0 0 8 Assignment request
1 0 0 1 9 Assignment request and direct assignment.
1 0 1 0 10 Assignment request and indirect assignment.
1 0 1 1 11 Assignment request, direct and indirect assignment.
1 1 0 0 12 Assignment request and through dynamic roles.
1 1 0 1 13 Assignment request, directly and through dynamic roles.
1 1 1 0 14 Assignment request, indirectly and through dynamic roles.
1 1 1 1 15 Assignment request, directly, indirectly and through dynamic roles.

Preparing Hierarchical Roles for Company Resource Assignments

One Identity Manager supplies a configuration, which support immediate usage of hierarchical roles for departments, cost centers, locations, and application roles. However, it may be necessary to make additional role assignments depending on the company structure.

You should check the following settings and make adjustments as required:

  • Specify whether employees, devices and workdesks and company resources may be assigned to roles.

    Employee, device, workdesk and company resource assignments are predefined for departments, cost centers, location and application roles.

  • Define the direction of inheritance with the hierarchy.

    Top down inheritance is defined for departments, cost centers, locations, and application roles.

  • Limit inheritance for specific roles if necessary.

    You can specify whether inheritance of company resources can be limited for single employees, devices or workdesks.

  • If necessary, define roles that are mutually exclusive.

    You can prevent employees, devices or workdesks being added to roles which contain mutually excluding company resources by specifying "conflicting roles".

Detailed information about this topic

Possible Assignments of Company Resources through Roles

Employees, devices and workdesks can inherit company resources though indirect assignment. To do this, employees, devices and workdesks may be members of as many roles as required. Employees, devices and workdesks obtain the necessary company resources through defined rules.

To assign company resources to roles, apply the appropriate tasks to the roles.

The following table shows the possible assignments of company resources to employees, workdesks, and devices using roles.

NOTE: Company resources are defined in the One Identity Manager modules and are not available until the modules are installed.
Table 4: Possible Assignments of Company Resources through Roles
 Assignable Company Resource Members in Roles
Employees Workdesks

Resources

possible

-

Account definitions possible  

Groups of custom target systems

possible (assigns to all an employee's custom defined target systems user accounts, for which group inheritance is authorized)

-

Active Directory groups

possible (assigns to all an employee's Active Directory user accounts and Active Directory contacts, for which group inheritance is authorized)

-

SharePoint groups

possible (assigns to all an employee's SharePoint user accounts)

-

SharePoint roles

possible (assigns to all an employee's SharePoint user accounts)

-

LDAP groups

possible (assigns to all an employee's LDAP user accounts for which group inheritance is authorized)

-

Notes groups

possible (assigns to all an employee's Notes user accounts)

-

SAP groups

possible (assigns to all an employee's SAP user accounts in the same SAP client.

-

SAP profiles

possible (assigns to all an employee's SAP user accounts in the same SAP client.

-

SAP roles

possible (assigns to all an employee's SAP user accounts in the same SAP client.

-

Structural profiles

possible (assigns to all an employee's SAP user accounts in the same SAP client.

-

BI analysis authorizations

possible (assigns to all an employee's BI user accounts in the same system)

-

Azure Active Directory groups

possible (assigns to all an employee's Azure Active Directory user accounts for which group inheritance is authorized)

-

Azure Active Directory administrator roles

possible (assigns to all an employee's Azure Active Directory user accounts for which group inheritance is authorized)

-

Azure Active Directory subscriptions

possible (assigns to all an employee's Azure Active Directory user accounts for which group inheritance is authorized)

-

Disabled Azure Active Directory service plans

possible (assigns to all an employee's Azure Active Directory user accounts for which group inheritance is authorized)

-

Unix groups

possible (assigns to all an employee's Unix user accounts)

-

PAM user groups

possible (assigns to all an employee's PAM user accounts for which group inheritance is authorized)

-

System roles

possible

possible

Subscribable reports

possible

-

Applications

possible

possible

Related Topics
Related Documents