Automatic creation of departments and locations based on user account information
You can create new departments and locations in One Identity Manager based on user account department and location data. Furthermore, departments, and locations are assigned to identities of the user accounts as primary department and primary location. These identities can obtain their company resources through these assignments if One Identity Manager is configured correspondingly.
Prerequisites for using this method
Identities must be created automatically when user accounts are added or modified. At least one of the following configuration parameters must be activated and the corresponding method implemented.
Table 13: Configuration Parameter for automatic identity assignment
|
TargetSystem | ADS | PersonAutoDefault |
Automatic identity assignment for user accounts added to the database outside synchronization based on the given mode. |
|
TargetSystem | ADS | PersonAutoFullsync |
Based on the given mode, automatic identity assignment is carried out on user accounts created or updated in the database by synchronization. |
|
TargetSystem | ADS | PersonUpdate |
Identities are updated continuously from linked user accounts. |
To implement this method
-
In the Designer, set the TargetSystem | ADS | AutoCreateDepartment configuration parameter to generate departments from the user account information.
-
In the Designer, set the TargetSystem | ADS | AutoCreateLocality configuration parameter to generate locations from the user account information.
Related topics
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 locked. 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
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.
Identities (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 identity (workdesk or device) is calculated from the position within the hierarchy and inheritance direction.
-
If you add an identity to roles and that identity owns an Active Directory user account, the Active Directory user account is added to the Active Directory group.
-
If you add an identity to roles and that identity 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 identities 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 identities after approval is granted.
Through system roles, Active Directory groups can be grouped together and assigned to identities 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:
|
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
