Chat now with support
Chat with Support

Identity Manager 8.0 - Administration Guide for Connecting to Azure Active Directory

Managing Azure Active Directory Environments Setting Up Synchronization with an Azure Active Directory Tenant Base Data for Managing Azure Active Directory Azure Active Directory Core Directories Azure Active Directory user accounts Azure Active Directory groups Azure Active Directory Administrator Roles Azure Active Directory Subscriptions and Service Plans
Azure Active Directory Subscriptions Disabled Azure Active Directory Service Plan
Reports about Azure Active Directory Objects Appendix: Configuration Parameters for Managing Azure Active Directory Appendix: Default Project Template for Azure Active Directory

Overview of Azure Active Directory Groups

Overview of Azure Active Directory Groups

Use this task to obtain an overview of the most important information about a group.

To obtain an overview of a group

  1. Select the category Azure Active Directory | Groups.
  2. Select the group in the result list.
  3. Select Azure Active Directory group overview in the task view.

Adding Azure Active Directory Groups to Azure Active Directory Groups

Adding Azure Active Directory Groups to Azure Active Directory Groups

Use this task to add a group to another group.

To assign groups directly to a group

  1. Select the category Azure Active Directory | Groups.
  2. Select the group in the result list.
  3. Select Assign groups in the task view.
  4. Assign child groups of the selected group in Add assignments.

    - OR -

    Remove assignments to groups in Remove assignments.

  5. Save the changes.

Effectiveness of Group Memberships

Table 39: Configuration Parameter for Conditional Inheritance
Configuration parameter Active Meaning

QER\Structures\Inherite\GroupExclusion

Preprocessor relevant configuration parameter for controlling effectiveness of group memberships. If the parameter is set, memberships can be reduced on the basis of exclusion definitions. The database has to be recompiled after changes have been made to the parameter.

When groups are assigned to user accounts an employee may obtain two or more groups, which are not permitted in this combination. To prevent this, you can declare mutually exclusive groups. To do this, you specify which of the two groups should apply to the user accounts if both are assigned.

It is possible to assign an excluded group directly, indirectly or by IT Shop request at any time. One Identity Manager determines whether the assignment is effective.

NOTE:

  • You cannot define a pair of mutually exclusive groups. That means, the definition "Group A excludes group B" AND "Group B excludes groups A" is not permitted.
  • You must declare each group to be excluded from a group separately. Exclusion definitions cannot be inherited.
  • One Identity Manager does not check whether membership of an excluded group is permitted in another group.

The effect of the assignments is mapped in the tables AADUserInGroup and AADBaseTreeHasGroup through the column XIsInEffect.

Example of the effect of group memberships
  • Group A is defined with permissions for triggering requests in a tenant. A group B is authorized to make payments. A group C is authorized to check invoices.
  • Group A is assigned through the department "Marketing", group B through "Finance" and group C through the business role "Control group".

Clara Harris has a user account in this tenant. She primarily belongs to the department "marketing". The business role "Control group" and the department "Finance" are assigned to her secondarily. Without an exclusion definition, the user account obtains all the permissions of groups A, B and C.

By using suitable controls, you want to prevent an employee from being able to trigger a request and to pay invoices. That means, groups A, B and C are mutually exclusive. An employee that checks invoices may not be able to make invoice payments as well. That means, groups B and C are mutually exclusive.

Table 40: Specifying excluded groups (table AADGroupExclusion)
Effective Group Excluded Group
Group A
Group B Group A
Group C Group B
Table 41: Effective Assignments
Employee Member in Role Effective Group
Ben King Marketing Group A
Jan Bloggs Marketing, finance Group B
Clara Harris Marketing, finance, control group Group C
Jenny Basset Marketing, control group Group A, Group C

Only the group C assignment is in effect for Clara Harris. It is published in the target system. If Clara Harris leaves the business role "control group" at a later date, group B also takes effect.

The groups A and C are in effect for Jenny Basset because the groups are not defined as mutually exclusive. That means that the employee is authorized to trigger request and to check invoices. If this should not be allowed, define further exclusion for group C.

Table 42: Excluded groups and effective assignments
Employee Member in Role Assigned Group Excluded Group Effective Group

Jenny Basset

 

Marketing Group A  

Group C

 

Control group Group C Group B

Group A

Prerequisites
  • The configuration parameter "QER\Inherite\GroupExclusion" is enabled.
  • Mutually exclusive groups belong to the same tenant.

To exclude a group

  1. Select the category Azure Active Directory | Groups.
  2. Select a group in the result list.
  3. Select Exclude groups in the task view.
  4. Assign the groups that are mutually exclusive to the selected group in Add assignments.

    - OR -

    Remove the conflicting groups that are no longer mutually exclusive in Remove assignments.

  5. Save the changes.

Azure Active Directory Group Inheritance Based on Categories

Azure Active Directory Group Inheritance Based on Categories

In One Identity Manager, groups, administrative roles, subscriptions and disabled service plans can be selectively inherited by user accounts. For this, groups(administrative roles, subscriptions and disabled service plans) and user accounts are divided into categories. The categories can be freely selected and are specified by a template. Each category is given a specific position within the template. The mapping rule contains different tables. Use the user account table to specify categories for target system dependent user accounts. Enter your categories for the structural profiles, administrative roles, subscriptions and disabled service plans in the other tables. Each table contains the category items "Position1" to "Position31".

Every user account can be assigned to one or more categories. Each group can also be assigned to one or more categories. The group is inherited by the user account when at least one user account category item matches an assigned group. The group is also inherited by the user account if the group or the user account is not put into categories.

NOTE: Inheritance through categories is only taken into account when groups are assigned indirectly through hierarchical roles. Categories are not taken into account when groups are directly assigned to user accounts.
Table 43: Category Examples
Category Position Categories for User Accounts Categories for Groups
1 Default user Default permissions
2 System user System user permissions
3 System administrator System administrator permissions

Figure 2: Example of inheriting through categories.

To use inheritance through categories

  • Define the categories in the tenant.
  • Assign categories to user accounts through their master data.
  • Assign categories to groups through their master data.
Related Topics
Related Documents