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 IT operating data for user accounts and which default values are used if no IT operating data can be determined through a person's primary roles.
The type of IT operating data 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, specify how the login names are formatted in the template.
-
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 the TargetSystem | 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. If necessary, modify the schedule in the Designer.
Related topics
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
provides you with support for creating complex password policies, for example, for system user passwords, the employees' central password as well as passwords for individual target systems. Password polices apply not only when the user enters a password but also when random passwords are generated.
Predefined password policies are supplied with the default installation that you can use or customize if required. You can also define your own password policies.
Detailed information about this topic
You can customize predefined password policies to meet your own requirements if necessary.
Password for logging in to
The password policy is applied for logging in to . This password policy defines the settings for the system user passwords (DialogUser.Password and Person.DialogUserPassword) as well as the passcode for a one time log in on the Web Portal (Person.Passcode).
NOTE: The password policy is marked as the default policy. This password policy is applied if no other password policy can be found for employees, user accounts, or system users.
For more information about password policies for employees, see the One Identity Manager Identity Management Base Module Administration Guide.
Password policy for forming employees' central passwords
An employee's central password is formed from the target system specific user accounts by respective configuration. The Employee central password policy defines the settings for the (Person.CentralPassword) central password. Members of the Identity Management | Employees | Administrators application role can adjust this password policy.
IMPORTANT: Ensure that the Employee central password policy does not violate the target system-specific requirements for passwords.
For more information about password policies for employees, see the One Identity Manager Identity Management Base Module Administration Guide.
Password policies for user accounts
Predefined password policies are provided, which you can apply to the user account password columns of the user accounts.
IMPORTANT: If you do not use password policies that are specific to the target system, the password policy default policy applies. In this case, ensure that the default policy does not violate the target systems requirements.
The E-Business Suite password policy is predefined for Oracle E-Business Suite systems. You can apply this password policy to user accounts (EBSUser.Password) of an E-Business Suite system.
If the E-Business Suite systems' password requirements differ, you should set up your own password policies for each system.
Furthermore, you can apply password policies based on the account definition of the user accounts or based on the manage level of the user accounts.
