Manually specifying application roles for PAM object owners
Application roles are created when owner are determined automatically. You can specify further application roles manually.
To specify an application role for a PAM object owner
-
In the Manager, select one of the following filters in the Privileged Account Management > Appliances > <appliance> > Privileged objects category.
-
To specify an application role for an asset, select Assets.
-
To specify an application role for an asset group. select Asset group.
-
To specify an application role for an asset account, select Asset account.
-
To specify an application role for a directory account, select Directory account.
-
To specify an application role for an account group, select Account group.
-
In the result list, select the PAM object.
-
Select the Change main data task.
-
On the General tab, select the application role in the Owner (Application Role) selection list.
- OR -
Next to the Owner (Application Role) list, click on 
to create a new application role.
-
Enter the application role name and assign the parent application role Privileged Account Governance | Asset and account owners.
-
Click OK to add the new application role.
-
Assign identities, who are owners, to the application role.
Related topics
Configuring PAM access request policies
Access requests for assets, asset accounts, directory accounts, asset groups, and account groups can only be requested if the One Identity Manager enabled option is activated in the access request policy.
To configure the access request policy
-
In the Manager, select the Privileged Account Management > Appliances > <Appliance> > Entitlements > <Entitlement> category.
-
Select the access request policy in the result list.
-
Select the Change main data task.
-
On the General tab, check the One Identity Manager enabled option.
-
If this option is set, access requests can be requested for assets, asset accounts, directory accounts, asset groups, and account groups that are within the access request policy's scope.
-
If this option is not set, is not possible to request access requests for assets, asset accounts, directory accounts, asset groups, and account groups that are within the access request policy's scope.
Related topics
Handling of PAM objects in the Web Portal
One Identity Manager enables its users to perform various tasks simply using a Web Portal.
-
Managing user accounts and identities
An account definition can be requested by shop customers in the Web Portal if it is assigned to an IT Shop shelf. The request undergoes a defined approval process. The user account is not created until it has been agreed by an authorized identity, such as a manager.
-
Managing assignments of user groups
When a group is assigned to an IT Shop shelf, the group can be requested by the customers of the shop in the Web Portal. The request undergoes a defined approval process. The group is not assigned until it has been approved by an authorized identity.
In the Web Portal, managers and administrators of organizations can assign groups to the departments, cost centers, or locations for which they are responsible. The groups are passed on to all persons who are members of these departments, cost centers, or locations.
If the Business Roles Module is available, managers, and administrators of business roles can assign groups in the Web Portal to the business roles for which they are responsible. The groups are passed on to all persons who are members of these business roles.
If the System Roles Module is available, supervisors of system roles can assign groups to the system roles in the Web Portal. The groups are passed on to all persons to whom these system roles are assigned.
-
Managing access requests to privileged objects
Through the Identity & Access Lifecycle > Privileged access IT Shop shelf, you can request password and session requests for the privileged objects of a PAM system. The request undergoes a defined approval process. The owner of the privileged object for which you are requesting access approves the order. In the PAM system, a corresponding access request is made. If you were able to successfully create the access request, the user can log on to the PAM system and call the required password, or start the required session.
-
Attestation
If the Attestation Module is available, the correctness of the properties of target system objects and of entitlement assignments can be verified on request. The owners of privileged objects attest the possible user access to these privileged objects. To enable this, attestation policies are configured in the Manager. The attestors use the Web Portal to approve attestation cases.
-
Governance administration
If the Compliance Rules Module is available, you can define rules that identify the invalid entitlement assignments and evaluate their risks. The rules are checked regularly, and if changes are made to the objects in One Identity Manager. Compliance rules are defined in the Manager. Supervisors use the Web Portal to check rule violations and to grant exception approvals.
If the Company Policies Module is available, company policies can be defined for the target system objects mapped in One Identity Manager and their risks evaluated. Company policies are defined in the Manager. Supervisors use the Web Portal to check policy violations and to grant exception approvals.
-
Risk assessment
You can use the risk index of groups to evaluate the risk of entitlement assignments for the company.One Identity Manager provides default calculation functions for this. The calculation functions can be modified in the Web Portal.
-
Reports and statistics
The Web Portal provides a range of reports and statistics about the identities, user accounts, and their entitlements and risks.
For more information about the named topics, see Managing PAM user accounts and identities, Assigning PAM user groups to PAM user accounts in One Identity Manager, PAM access requests and refer to the following guides:
-
One Identity Manager Web Designer Web Portal User Guide
-
One Identity Manager Attestation Administration Guide
-
One Identity Manager Compliance Rules Administration Guide
-
One Identity Manager Company Policies Administration Guide
-
One Identity Manager Risk Assessment Administration Guide
Basic data for managing a Privileged Account Management system
To manage a Privileged Account Management system in One Identity Manager, the following basic data is relevant.
- Account definitions
One Identity Manager has account definitions for automatically allocating user accounts to identities. You can create account definitions for every target system. If an identity does not yet have a user account in a target system, a new user account is created. This is done by assigning account definitions to an identity.
For more information, see Account definitions for PAM user accounts.
- Password policies
provides you with support for creating complex password policies, for example, for system user passwords, the identities' 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.
For more information, see Password policies for PAM users.
- Target system types
Target system types are required for configuring target system comparisons. Tables with outstanding objects are maintained with the target system types and settings are configured for provisioning memberships and single objects synchronization. Target system types also map objects in the Unified Namespace.
For more information, see Post-processing outstanding objects.
- Target system managers
A default application role exists for the target system manager in One Identity Manager. Assign identities to this application role who have permission to edit all appliances in One Identity Manager.
Define additional application roles if you want to limit the permissions for target system managers to individual appliances. The application roles must be added under the default application role.
For more information, see Target system managers for PAM systems.
- Servers
In order to handle target system specific processes in One Identity Manager, the synchronization server and its server functionality must be declared.
For more information, see Job server for PAM-specific process handling.
-
Owners of privileged objects
One Identity Manager includes a standard application role for the owners of privileged objects such as PAM assets, PAM asset accounts or PAM directory accounts. The owners are included in the standard approval workflows as approvers and attestors.
For more information, see PAM object owners.
