An administrative user account must be used for certain administrative tasks. Administrative user accounts are usually predefined by the target system and have fixed names and login names, such as Administrator.
Administrative user accounts are imported into One Identity Manager during synchronization.
NOTE: Some administrative user accounts can be automatically identified as privileged user accounts. To do this, in the Designer, enable the Mark selected user accounts as privileged schedule.
You can label administrative user accounts as a Personalized administrator identity or as a Shared identity. Proceed as follows to provide the employees who use this user account with the required permissions.
Related topics
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).
NOTE: The criteria according to which user accounts are automatically identified as privileged are defined as extensions to the view definition (ViewAddOn) in the TSBVAccountIsPrivDetectRule table (which is a table of the Union type). The evaluation is done in the TSB_SetIsPrivilegedAccount script.
To create privileged users through account definitions
- Create an account definition. Create a new manage level for privileged user accounts and assign this manage level to the account definition.
- If you want to prevent the properties for privileged user accounts from being overwritten, set the IT operating data overwrites property for the manage level to Only initially. In this case, the properties are populated just once when the user accounts are created.
- Specify the effect of temporarily or permanently disabling or deleting, or the security risk of an employee on its user accounts and group memberships for each manage level.
- Create a formatting rule for the 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 settings are recommended for privileged user accounts:
- In the mapping rule for the IsPrivilegedAccount column, use the default value 1 and set the Always use default value option.
- You can also specify a mapping rule for the IdentityType column. The column owns different permitted values that represent user accounts.
- To prevent privileged user accounts from inheriting the entitlements of the default user, define a mapping rule for the IsGroupAccount column with a default value of 0 and set the Always use default value option.
- Enter the effective IT operating data for the target system.
Specify in the departments, cost centers, locations, or business roles which IT operating data should apply when you set up a user account.
- Assign the account definition directly to employees who work with privileged user accounts.
When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.
TIP: If customization requires that the login names of privileged user accounts follow a defined naming convention, create the template according to which the login names are formed.
- To use a prefix for the login name, in the Designer, set the TargetSystem | EBS | Accounts | PrivilegedAccount | AccountName_Prefix configuration parameter.
- To use a postfix for the login name, in the Designer, set theTargetSystem | EBS | Accounts | PrivilegedAccount | AccountName_Postfix configuration parameter.
These configuration parameters are evaluated in the default installation, if a user account is marked with the Privileged user account property (IsPrivilegedAccount column). The user account login names are renamed according to the formatting rules. This also occurs if the user accounts are labeled as privileged using the Mark selected user accounts as privileged schedule.
Related topics
Assign employees who use the user account in the target system to an administrative user account with a shared identity. Only employees with Primary identity can be assigned.
To assign employees with user permissions
-
Select the Oracle E-Business Suite | User accounts category.
-
In the result list, select the user account with a shared identity.
-
Select the Assign employees authorized to use task.
- In the Add assignments pane, assign employees.
- OR -
In the Remove assignments pane, remove employees.
- Save the changes.
Provision of login information
When new user accounts are created in One Identity Manager, the passwords needed to log in to the target system are created immediately also. Various options are available for assigning the initial password. Predefined password policies are applied to the passwords, and you can adjust these policies to suit your individual requirements if necessary. You can set up email notifications to distribute the login information generated to users.
Detailed information about this topic
