Chat now with support
Chat with Support

Identity Manager 8.1.5 - Administration Guide for Connecting to IBM Notes

Managing IBM Notes environments Setting up IBM Notes synchronization Basic configuration data Notes domains Notes certificates Notes templates Notes policies Notes user accounts Notes groups Mail-in databases Notes server Using AdminP requests for handling IBM Notes processes Reports about Notes domains Configuration parameters for synchronizing a Notes domain Default project template for IBM Notes

Assigning Notes servers to a Notes group

You can assign Notes servers directly to a group.

To assign servers to a group

  1. Select the IBM Notes | Groups category.
  2. Select the group in the result list.
  3. Select the Assign members task.
  4. Select the Server tab.
  5. In the Add assignments pane, assign the servers. To filter the servers shown, select a domain in the Notes domains field.

    - OR -

    In the Remove assignments pane, remove the servers.

  6. Save the changes.
Related topics

Adding Notes groups to Notes groups

You can assign parent or child groups to a Notes group.

To assign child groups

  1. Select the IBM Notes | Groups category.
  2. Select the group in the result list.
  3. Select the Assign members task.
  4. Select the Groups tab.
  5. In the Add assignments pane, assign child groups. To filter the groups, select a domain in the Notes Domains input field.

    - OR -

    In the Remove assignments pane, remove the child groups.

  6. Save the changes.

To assign parent groups

  1. Select the IBM Notes | Groups category.
  2. Select the group in the result list.
  3. Select the Assign parent groups task.
  4. In the Add assignments pane, assign parent groups. To filter the groups, select a domain in the Notes Domains input field.

    - OR -

    In the Remove assignments pane, remove the parent groups.

  5. Save the changes.
Related topics

Effectiveness of group memberships

Table 46: Configuration parameters for conditional inheritance
Configuration parameter Effect when set

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. Changes to this parameter require the database to be recompiled.

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 at any time either directly, indirectly, or with an IT Shop request. 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 if membership of an excluded group is permitted in another group (NDOGroupInGroup table).

The effectiveness of the assignments is mapped in the NDOUserInGroup and BaseTreeHasNDOGroup tables by the XIsInEffect column.

Example of the effect of group memberships
  • The groups A, B, and C are defined in a domain.
  • Group A is assigned through the "Marketing" department, group B through "Finance", and group C through the "Control group" business role.

Clara Harris has a user account in this domain. She primarily belongs to the "Marketing" department. The "Control group" business role and the "Finance" department 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 obtaining authorizations of groups A and group B at the same time. That means, groups A, B, and C are mutually exclusive. A user, who is a member of group C cannot be a member of group B at the same time. That means, groups B and C are mutually exclusive.

Table 47: Specifying excluded groups (NDOGroupExclusion table)

Effective group

Excluded group

Group A

Group B

Group A

Group C

Group B

Table 48: 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 "control group" business role 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. If this should not be allowed, define further exclusion for group C.

Table 49: 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 QER | Structures | Inherite | GroupExclusion configuration parameter is set.

  • Mutually exclusive groups belong to the same domain

To exclude a group

  1. In the Manager, select the IBM Notes | Groups category.

  2. Select a group in the result list.

  3. Select the Exclude groups task.

  4. In the Add assignments pane, assign the groups that are mutually exclusive to the selected group.

    - OR -

    In the Remove assignments pane, remove the groups that are not longer mutually exclusive.

  5. Save the changes.

Notes group inheritance based on categories

In One Identity Manager, groups can be selectively inherited by user accounts. For this purpose, the groups and the user accounts are divided into categories. The categories can be freely selected and are specified using a mapping rule. Each category is given a specific position within the template. The template contains two tables; the user account table and the group table. Use the user account table to specify categories for target system dependent user accounts. In the group table enter your categories for the target system-dependent groups. Each table contains the Position 1 to Position 31 category positions.

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 items 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 50: Category examples
Category item Categories for user accounts Categories for groups
1 Default user Default permissions
2 System users System user permissions
3 System administrator System administrator permissions

Figure 2: Example of inheriting through categories.

To use inheritance through categories

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

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating