Assigning account definitions to linked PAM user accounts
An account definition can be subsequently assigned to user accounts with Linked status. This may be necessary, for example, if:
- Employees and user accounts were linked manually
- Automatic employee assignment is configured, but when a user account is inserted, no account definition is assigned in the appliance.
To select user accounts through account definitions
- Create an account definition.
- Assign an account definition to the appliance.
- Assign a user account in the Linked state to the account definition. The account definition's default manage level is applied to the user account.
-
In the Manager, select the Privileged Account Management | User accounts | Linked but not configured | <Appliance> category.
- Select the Assign account definition to linked accounts task.
-
In the Account definition menu, select the account definition.
-
Select the user accounts that contain the account definition.
- Save the changes.
Detailed information about this topic
Manually linking employees to PAM user accounts
An employee can be linked to multiple PAM user accounts, for example, so that you can assign an administrative user account in addition to the default user account. One employee can also use default user accounts with different types.
NOTE: To enable working with identities for user accounts, the employees also need identities. You can only link user accounts to which an identity is assigned with employees who have this same identity.
To manually assign user accounts to an employee
-
In the Manager, select the Employees | Employees category.
-
Select the employee in the result list and run the Assign PAM user accounts task.
-
Assign the user accounts.
- Save the changes.
Related topics
Supported user account types
Different types of user accounts, such as default user accounts, administrative user accounts, service accounts, or privileged user accounts, can be mapped in One Identity Manager.
The following properties are used for mapping different user account types.
-
Identity
The Identity property (IdentityType column) is used to describe the type of user account.
Table 14: Identities of user accounts
| Primary identity |
Employee's default user account. |
Primary |
| Organizational identity |
Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas. |
Organizational |
| Personalized admin identity |
User account with administrative permissions, used by one employee. |
Admin |
| Sponsored identity |
User account that is used for a specific purpose, such as training. |
Sponsored |
| Shared identity |
User account with administrative permissions, used by several employees. |
Shared |
| Service identity |
Service account. |
Service |
NOTE: To enable working with identities for user accounts, the employees also need identities. You can only link user accounts to which an identity is assigned with employees who have this same identity.
The primary identity, the organizational identity, and the personalized admin identity are used for different user accounts, which can be used by the same actual employee to perform their different tasks within the company.
To provide user accounts with a personalized admin identity or an organizational identity for an employee, you create subidentities for the employee. These subidentities are then linked to user accounts, enabling you to assign the required permissions to the different user accounts.
User accounts with a sponsored identity, group identity, or service identity are linked to dummy employees that do not refer to a real person. These dummy employees are needed so that permissions can be inherited by the user accounts. When evaluating reports, attestations, or compliance checks, check whether dummy employees need to be considered separately.
For detailed information about mapping employee identities, see the One Identity Manager Identity Management Base Module Administration Guide.
-
Privileged user account
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 labeled with the Privileged user account property (IsPrivilegedAccount column).
Detailed information about this topic
Default user accounts
Normally, each employee obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the employee. The effect of the link and the scope of the employee’s inherited properties on the user accounts can be configured through an account definition and its manage levels.
To create default user accounts through account definitions
- Create an account definition and assign the Unmanaged and Full managed manage levels.
- Specify the effect of temporarily or permanently disabling, deleting, or the security risk of an employee on its user accounts and group memberships for each manage level.
- Create a formatting rule for IT operating data.
You use the mapping rule to define which rules are used to map the IT operating data for the user accounts, and which default values are used if no IT operating data can be determined through a person's primary roles.
Which IT operating data is required depends on the target system. The following setting are recommended for default user accounts:
- In the mapping rule for the IsGroupAccount column, use the default value 1 and enable the Always use default value option.
- In the mapping rule for the IdentityType column, use the default value Primary and enable Always use default value.
- Enter the effective IT operating data for the target system. Select the concrete target system under Effects on.
Specify in the departments, cost centers, locations, or business roles that IT operating data should apply when you set up a user account.
- Assign the account definition to employees.
When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.
Related topics
