Chatta subito con l'assistenza
Chat con il supporto

Identity Manager 9.1.1 - Administration Guide for Connecting to Active Directory

Managing Active Directory environments Synchronizing an Active Directory environment
Setting up initial synchronization with an Active Directory domain Adjusting the synchronization configuration for Active Directory environments Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization Pausing handling of target system specific processes (Offline mode)
Managing Active Directory user accounts and employees
Account definitions for Active Directory user accounts and Active Directory contacts Assigning employees automatically to Active Directory user accounts Supported user account types Updating employees when Active Directory user account are modified Automatic creation of departments and locations based on user account information Specifying deferred deletion for Active Directory user accounts and Active Directory contacts
Managing memberships in Active Directory groups Login information for Active Directory user accounts Mapping of Active Directory objects in One Identity Manager
Active Directory domains Active Directory container structures Active Directory user accounts Active Directory contacts Active Directory groups Active Directory computers Active Directory security IDs Active Directory printers Active Directory sites Reports about Active Directory objects
Handling of Active Directory objects in the Web Portal Basic data for managing an Active Directory environment Configuration parameters for managing an Active Directory environment Default project template for Active Directory Processing methods of Active Directory system objects Active Directory connector settings

Specifying deferred deletion for Active Directory user accounts and Active Directory contacts

You can use deferred deletion to specify how long the user accounts remain in the database after deletion is triggered before they are finally removed. By default, user accounts are finally deleted from the database after 30 days. First, the user accounts are disabled or blocked. You can reenable the user accounts up until deferred deletion runs. After deferred deletion is run, the user accounts are deleted from the database and cannot be restored anymore.

You have the following options for configuring deferred deletion.

  • Global deferred deletion: Deferred deletion applies to user accounts in all target system. The default value is 30 days.

    In the Designer, enter a different value for deferred deletion in the Deferred deletion [days] property of the ADSAccount and the ADSContact tables.

  • Object-specific deferred deletion: Deferred deletion can be configured depending on certain properties of the accounts.

    To use object-specific deferred deletion, in the Designer, create a Script (deferred deletion) for the ADSAccount and ADContact tables.

    Example:

    Deferred deletion of privileged user accounts is 10 days. The following Script (deferred deletion) is entered in the table.

    If Not $IsPrivilegedAccount:Bool$ Then

    Value = 10

    End If

For more information on editing table definitions and configuring deferred deletion in the Designer, see the One Identity Manager Configuration Guide.

Managing memberships in Active Directory groups

Active Directory user accounts, Active Directory contacts, and Active Directory computers can be grouped into Active Directory groups that can be used to regulate access to resources.

In One Identity Manager, you can assign Active Directory groups directly to user accounts, contacts, and computers or they can be inherited through departments, cost centers, locations, or business roles. Users can also request the groups through the Web Portal. To do this, groups are provided in the IT Shop.

Detailed information about this topic

Assigning Active Directory groups to Active Directory user accounts, Active Directory contacts, and Active Directory computers

Active Directory groups can be assigned directly or indirectly to Active Directory user accounts, Active Directory contacts, and Active Directory computers.

Employees (workdesks or devices) and Active Directory groups are grouped into hierarchical roles in the case of indirect assignment. The number of Active Directory groups assigned to an employee (workdesk or device) is calculated from the position within the hierarchy and inheritance direction.

  • If you add an employee to roles and that employee owns an Active Directory user account, the Active Directory user account is added to the Active Directory group.

  • If you add an employee to roles and that employee owns an Active Directory contact, the Active Directory contact is added to the Active Directory group.

  • If you add a device to roles, the Active Directory computer that references the device is added to the Active Directory groups.

  • If a device owns a workdesk and you add the workdesk to roles, the Active Directory computer, which references this device, is also added to all Active Directory groups of the workdesk's roles.

Furthermore, Active Directory groups can be requested through the Web Portal. To do this, add employees to a shop as customers. All Active Directory groups are assigned to this shop can be requested by the customers. Requested Active Directory groups are assigned to the employees after approval is granted.

Through system roles, Active Directory groups can be grouped together and assigned to employees and workdesks as a package. You can create system roles that contain only Active Directory groups. You can also group any number of company resources into a system role.

To react quickly to special requests, you can also assign Active Directory groups directly to Active Directory user accounts and Active Directory computers.

For more information see the following guides:

Topic

Guide

Basic principles for assigning and inheriting company resources

One Identity Manager Identity Management Base Module Administration Guide

One Identity Manager Business Roles Administration Guide

Assigning company resources through IT Shop requests

One Identity Manager IT Shop Administration Guide

System roles

One Identity Manager System Roles Administration Guide

Detailed information about this topic

Prerequisites for indirect assignment of Active Directory groups

Employees (workdesks or devices) and Active Directory groups are grouped into hierarchical roles in the case of indirect assignment. When assigning Active Directory groups indirectly, check the following settings and modify them if necessary.

Prerequisites for indirect assignment of Active Directory groups to Active Directory user accounts and Active Directory contacts

  1. Assignment of employees and Active Directory groups is permitted for role classes (departments, cost centers, locations, or business roles).

  2. The Active Directory user accounts and Active Directory contacts are linked to employees.

  3. Active Directory user accounts and Active Directory contacts are labeled with the Groups can be inherited option.

Prerequisites for indirect assignment of Active Directory groups to Active Directory computers

  1. Assignment of devices and Active Directory groups is permitted for role classes (departments, cost centers, locations, or business roles).

  2. The Active Directory computer is connected to a device.

  3. The device is labeled as a PC or server.

  4. The TargetSystem | ADS | HardwareInGroupFromOrg configuration parameter is set.

Prerequisites for indirect assignment to Active Directory groups to Active Directory computers through workdesks

  1. Assignment of workdesks and groups is permitted for the role class (department, cost center, location, or business role).

  2. The computer is connected to a device labeled as PC or server. This device owns a workdesk.

ClosedAllow assignments to role classes of departments, cost centers, locations, or roles

NOTE: There are other configuration settings that play a role when company resources are inherited through departments, cost centers, locations, and business roles. For example, role inheritance might be blocked or inheritance of employees, devices or workdesks not allowed. For more detailed information about the basic principles for assigning company resources, see the One Identity Manager Identity Management Base Module Administration Guide.

Related topics
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione