Employee |
Employee that uses this user account. An employee is already entered if the user account was generated by an account definition. If you create the user account manually, you can select an employee in the menu. If you are using automatic employee assignment, an associated employee is found and added to the user account when you save the user account.
You can create a new employee for a user account with an identity of type Organizational identity, Personalized administrator identity, Sponsored identity, Shared identity, or Service identity. To do this, click next to the input field and enter the required employee main data. Which login data is required depends on the selected identity type. |
No link to an employee required |
Specifies whether the user account is intentionally not assigned an employee. The option is automatically set if a user account is included in the exclusion list for automatic employee assignment or a corresponding attestation is carried out. You can set the option manually. Enable the option if the user account does not need to be linked with an employee (for example, if several employees use the user account).
If attestation approves these user accounts, these user accounts will not be submitted for attestation in the future. In the Web Portal, user accounts that are not linked to an employee can be filtered according to various criteria. |
Not linked to an employee |
Indicates why the No link to an employee required option is enabled for this user account. Possible values:
-
By administrator: The option was set manually by the administrator.
-
By attestation: The user account was attested.
-
By exclusion criterion: The user account is not associated with an employee due to an exclusion criterion. For example, the user account is included in the exclude list for automatic employee assignment (configuration parameter PersonExcludeList). |
Account definition |
Account definition through which the user account was created.
Use the account definition to automatically fill user account main data and to specify a manage level for the user account. One Identity Manager finds the IT operating data of the assigned employee and enters it in the corresponding fields in the user account.
NOTE: The account definition cannot be changed once the user account has been saved.
NOTE: Use the user account's Remove account definition task to reset the user account to Linked status. This removes the account definition from both the user account and the employee. The user account remains but is not managed by the account definition anymore. The task only removes account definitions that are directly assigned (XOrigin=1). |
Manage level |
Manage level of the user account. Select a manage level from the menu. You can only specify the manage level can if you have also entered an account definition. All manage levels of the selected account definition are available in the menu. |
First name |
The user’s first name. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
Middle name |
User's middle name. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
Last name |
The user’s last name. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
Initials |
The user’s initials. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
Title |
The user’s academic title. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
Name |
User account identifier. The identifier is made up of the user’s first and last names. |
Distinguished name |
User account's distinguished name. The distinguished name is formatted from the user account's identifier and the container and cannot be changed. |
Domain |
Domain in which the user account is created. |
Container |
Container in which to create the user account. If you have assigned an account definition, the container is determined from the company IT data for the assigned employee depending on the manage level of the user account. When the container is selected, the defined name for the user is created using a formatting rule. |
Primary group |
User account's primary group. Synchronization with the Active Directory environment assigns the user account to the Domain Users group by default. Only groups that are assigned to the user account are available as primary groups. |
Login name (pre Win2000) |
Login name for the previous version of Active Directory. If you assigned an account definition, the login name (pre Win2000) is made up of the employee’s central user account depending on the manage level of the user account. |
User login name |
User account login name. User login names that are formatted like this correspond to the User Principal Name (UPN) in Active Directory.
If you have already established the container and entered the login name (pre Win2000), the user login name is created following the formatting rule as shown:
<login name (pre Win2000)>@<AD domain name> |
Email address |
User account email address. If you assigned an account definition, the email address is made up of the employee’s default email address depending on the manage level of the user account. |
Additional email addresses |
Other email addresses for the user account. |
Account expiry date |
Account expiry date. Specifying an expiry data for the account has the effect that the logon for this user account is blocked as soon as the given date is exceeded. If you assigned an account definition, the employee’s last day of work it is automatically taken as the expiry date depending on the manage level. Any existing account expiry date is overwritten in this case. |
Structural object class |
Structural object class representing the object type. By default, you set up user accounts in One Identity Manager with the USER object class. However, the INETORGPERSON object class is also supported, which is used by other LDAP and X.500 directory services for the mapping of user accounts. |
Risk index (calculated) |
Maximum risk index value of all assigned groups. The property is only visible if the QER | CalculateRiskIndex configuration parameter is set. For more information, see the One Identity Manager Risk Assessment Administration Guide. |
Category |
Categories for the inheritance of groups by the user account. Groups can be selectively inherited by user accounts. To do this, groups and user accounts or contacts are divided into categories. Select one or more categories from the menu. |
Description |
Text field for additional explanation. |
Identity |
User account's identity type Permitted values are:
-
Primary identity: Employee's default user account.
-
Organizational identity: Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.
-
Personalized administrator identity: User account with administrative permissions, used by one employee.
-
Sponsored identity: User account to use for a specific purpose. Training, for example.
-
Shared identity: User account with administrative permissions, used by several employees. Assign all employees that use this user account.
-
Service identity: Service account.
|
Privileged user account. |
Specifies whether this is a privileged user account. |
Groups can be inherited |
Specifies whether the user account can inherit groups through the linked employee. If the option is set, the user account inherits groups through hierarchical roles, in which the employee is a member, or through IT Shop requests.
-
If you add an employee with a user account to a department, for example, and you have assigned groups to this department, the user account inherits these groups.
-
If an employee has requested group membership in the IT Shop and the request is granted approval, the employee's user account only inherits the group if the option is set. |
Preferred user account |
Preferred user account when an employee has several user accounts in Active Directory. |
User account is disabled |
Specifies whether the user account is disabled. If a user account is not required for a period of time, you can temporarily disable the user account by using the <User account is deactivated> option. |
Account locked |
Specifies whether the user account is locked. Depending on the configuration, the user account in the Active Directory environment is locked after multiple incorrect password attempts. You can lock the user account again in the Manager using the Unlock user account task.
If the user account is linked to an employee, the user account is unlocked when a new central password is set for the employee. This behavior is controlled by the TargetSystem | ADS | Accounts | UnlockByCentralPassword configuration parameter. For more information about an employee’s central password, see One Identity Manager Identity Management Base Module Administration Guide. |
Protected from accidental deletion |
Specifies whether to protect the user account against accidental deletion. If the option is set, the permissions for deleting the user account are removed in Active Directory. The user account cannot be deleted or moved. |