Privileged user accounts are used to provide employees with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are marked with the property Privileged user account (IsPrivilegedAccount).
|
NOTE: The criteria used to label user accounts automatically as privileged, are defined as extensions to the view definition (ViewAddOn) on the table TSBVAccountIsPrivDetectRule (table type "Union"). The evaluation is done in the script TSB_SetIsPrivilegedAccount. |
To create privileged users through account definitions
An account definition specifies which rules are used to generate the IT operating data for example, whether the container for a user account is made up of the employee's department, cost center, location or business role and which default values will be used if no IT operating data can be found through the employee's primary roles.
Which IT operating data is required, depends on the target system. The following settings are recommended for privileged user accounts:
Specify in the departments, cost centers, locations or business roles, which IT operating data should apply when you set up a user account.
When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.
|
NOTE: Specify a formatting rule for a naming schema if it is required by the company for privileged user account login names. To use a prefix with a login name, set the configuration parameter These configuration parameters are evaluated in the default installation, if a user account is marked with the property Privileged user account (IsPrivilegedAccount). The user account login names are renamed according to the formatting rules. This also takes place if the user accounts are labeled as privileged by the schedule "Mark selected user accounts as privileged". |
A user account can be linked to an employee in the One Identity Manager. You can also manage user accounts separately from employees.
|
NOTE: It is recommended to use account definitions to set up user accounts for company employees. In this case, some of the master data described in the following is mapped through templates from employee master data. |
|
NOTE: If employees obtain their user accounts through account definitions, they have to have a central user account |
To edit master data for a user account
- OR-
Click in the result list toolbar.
To manually assign or create a user account for an employee
Enter the following data on the General tab:
Property | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Host |
The user account's host. | ||||||||||||||
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 use automatic employee assignment, an associated employee is created and entered into the user account when the user account is saved. | ||||||||||||||
Account definition |
Account definition through which the user account was created. Use the account definition to automatically fill user account master data and to specify a manage level for the user account. The One Identity Manager finds the IT operating data of the assigned employee and enters it in the corresponding fields in the user account.
To create the user account manually through an account definition, enter an employee in the Employee box. You can select all the account definitions assigned to this employee and through which no user account has been created for this employee. | ||||||||||||||
Manage level |
User account's manage level. 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. | ||||||||||||||
Login shell |
Shell that is executed if a user logs in to Unix using a terminal based login. | ||||||||||||||
User name |
Name of the user account for logging in to a Unix host. If an account definition is assigned, this field is automatically filled with the employee's central user account depending on the manage level. | ||||||||||||||
User ID |
User ID for the user account in the Unix host. | ||||||||||||||
Password |
Password for the user account. Depending on the configuration parameter "Person\UseCentralPassword" the employee’s central password can be mapped to the user account‘s password. If you use an initial password for the user accounts, it is automatically entered when a user account is created.
| ||||||||||||||
Password confirmation |
Reconfirm password. | ||||||||||||||
Primary group ID | Identifier of the user account's primary group. | ||||||||||||||
Primary group |
Name of the user account's primary group. This defines the group ownership of files created by the user. A user account's primary group is determined as follows:
| ||||||||||||||
Home directory |
The user's full home directory path, for example /home/user001. | ||||||||||||||
Risk index (calculated) |
Maximum risk index values for all assigned | ||||||||||||||
Category |
Categories for the inheritance of groups by the user account. Select one or more categories from the menu. Groups can be selectively inherited by user accounts. To do this, groups and user accounts or contacts are divided into categories. | ||||||||||||||
Comment (GECOS) |
Spare text box for additional explanation. Additional information about the user account, which is found in the GECOS in /etc/password. If an account definition is assigned, this field is automatically filled with the employee's internal name depending on the manage level. | ||||||||||||||
Identity |
User account's identity type
| ||||||||||||||
Groups can be inherited |
Specifies whether the user account groups can inherit through the employee. If this option is set, the user account inherits groups through hierarchical roles or IT Shop requests.
| ||||||||||||||
Privileged user account |
Specifies whether this is a privileged user account. |
You can enter additional master data for user accounts in an IBM AIX system, like limits, password data, security data or information about encrypting the file system. This data is shown if the host is labeled with the option AIX system.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy