Converse agora com nosso suporte
Chat com o suporte

Identity Manager 9.1.1 - Administration Guide for Privileged Account Governance

About this guide Managing a Privileged Account Management system in One Identity Manager Synchronizing a Privileged Account Management system
Setting up the initial synchronization of a One Identity Safeguard Customizing the synchronization configuration for One Identity Safeguard Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization Pausing handling of target system specific processes (Offline mode)
Managing PAM user accounts and employees Managing assignments of PAM user groups Login information for PAM user accounts Mapping of PAM objects in One Identity Manager PAM access requests Handling of PAM objects in the Web Portal Basic data for managing a Privileged Account Management system Configuration parameters for managing a Privileged Account Management system Default project template for One Identity Safeguard Editing One Identity Safeguard system objects One Identity Safeguard connector settings Known issues about connecting One Identity Safeguard appliances

Creating certificate-based PAM user accounts

The users of a certificate-based PAM user account are authenticated using a certificate in the Privileged Account Management system.

To create a certificate-based PAM user account

  1. In the Manager, select the Privileged Account Management > User accounts category.

  2. Click in the result list.

  3. On the General tab, enter the following data as a minimum:

    • Appliance: Appliance to which the user account belongs.

    • Identity provider: Select the Local value.

    • User name: Enter the name to display.

    • Authentication provider: Select Certificate.

    • Certificate thumbprint (SHA-1): Enter the unique hash value (40 hexadecimal characters) of the certificate.

      NOTE: You can copy the thumbprint value directly from the certificate and insert it here, including blank characters.

    • Time zone: The user's time zone. The default time zone is UTC (Coordinated Universal Time).

  4. Save the changes.
Related topics

Creating PAM user accounts for directory users

Directory users are user accounts from an external target system, for example Active Directory or LDAP.

You can only create directory users in One Identity Manager if the Active Directory environment or the LDAP environment is imported into the One Identity Manager.

To create a PAM user account for directory users

  1. In the Manager, select the Privileged Account Management > User accounts category.

  2. Click in the result list.

  3. On the General tab, enter the following data as a minimum:

    • Appliance: Appliance to which the user account belongs.

    • Identity provider: Root domain of the respective directory server.

    • Identity object: Select the user account from the identity provider.

      1. To do this, click next to the input field and enter the following information:

        • Table: Table in which the user accounts are mapped. This table is preselected.

          For an Active Directory user account, ADSAccount is selected. For an LDAP user account, LDAPAccount is selected.

        • Identity object: Select the user account.

      2. Click OK.

      The domain, the user name, and the display name are determined from the user account.

    • Authentication provider: Select how the user is authenticated in the Privileged Account Management system. Depending on the authentication provider, other data may be required.

      • <Directory name>: Select the user account’s Active Directory or LDAP domain.

        You have the option to specify whether an Active Directory domain requires certificate authentication or not. Set the Require certificate authentication if the user requires their domain issued user certificate or SmartCard to log in.

      • <External organization>: Enter the email address or the name claim.

      • <RADIUS server>: Enter the login name of the RADIUS server.

    • Time zone: The user's time zone. The default time zone is UTC (Coordinated Universal Time).

  4. Save the changes.

NOTE: If you use account definitions to create PAM user accounts for employees, for a PAM appliance, you have the option to define an Active Directory or LDAP account definition as a required account definition. In this case, an Active Directory or LDAP user account is first created for the employee. If this user account exists, the PAM user account is created as a directory user.

Related topics

Editing main data of PAM user accounts

To edit main data of a user account

  1. In the Manager, select the Privileged Account Management > User accounts category.

  2. Select the user account in the result list.

  3. Select the Change main data task.

  4. Edit the user account's resource data.

  5. Save the changes.
Related topics

General main data of PAM user accounts

On the General tab, you enter the following main data:

Table 22: Additional main data of a user account

Property

Description

Appliance

Appliance to which the user account belongs.

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 are using automatic employee assignment, an associated employee is found and added to the user account when you save the user account.

You can create a new employee for a user account with an identity of type Organizational identity, Personalized administrator identity, Sponsored identity, Shared identity, or Service identity. To do this, click next to the input field and enter the required employee main data. Which login data is required depends on the selected identity type.

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.

No link to an employee required

Specifies whether the user account is intentionally not assigned an employee. The option is automatically set if a user account is included in the exclusion list for automatic employee assignment or a corresponding attestation is carried out. You can set the option manually. Enable the option if the user account does not need to be linked with an employee (for example, if several employees use the user account).

If attestation approves these user accounts, these user accounts will not be submitted for attestation in the future. In the Web Portal, user accounts that are not linked to an employee can be filtered according to various criteria.

Not linked to an employee

Indicates why the No link to an employee required option is enabled for this user account. Possible values:

  • By administrator: The option was set manually by the administrator.

  • By attestation: The user account was attested.

  • By exclusion criterion: The user account is not associated with an employee due to an exclusion criterion. For example, the user account is included in the exclude list for automatic employee assignment (configuration parameter PersonExcludeList).

Account definition

Account definition through which the user account was created.

Use the account definition to automatically fill user account main data and to specify a manage level for the user account. One Identity Manager finds the IT operating data of the assigned employee and enters it in the corresponding fields in the user account.

NOTE: The account definition cannot be changed once the user account has been saved.

NOTE: Use the user account's Remove account definition task to reset the user account to Linked status. This removes the account definition from both the user account and the employee. The user account remains but is not managed by the account definition anymore. The task only removes account definitions that are directly assigned (XOrigin=1).

Manage level

Manage level of the user account. 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.

Identity provider

Source from which the user’s personal information is taken from. Permitted values are:

  • Local: Local PAM user account. You can enter contact data for this user account.

  • <Directory name>: External identity provider. Root domain of the respective directory server, for example, Active Directory or LDAP. Contact data are taken from the Active Directory or the LDAP user account.

    This variant is only available if the Active Directory domain or the LDAP domain is imported into the One Identity Manager.

Identity object

User account in Active Directory or LDAP.

Authentication provider

Specifies how the user is authenticated in the Privileged Account Management system. Permitted values are:

  • Certificate: (Only for local identity providers) Authentication is performed using a certificate.

  • Local: (Only for local identity providers) The user is authenticated by a user name and password.

  • <Directory name>: (Only for local identity providers) The identity object’s domain. Authentication takes place through a user account of the relevant directory service, for example Active Directory user account or LDAP user account.

    This variant is only available if the Active Directory domain or the LDAP domain is imported into the One Identity Manager.

  • <External federation>: Name of an external organization. The given email address or the name claim used for authentication.

  • <RADIUS server>: Name of the RADIUS server. Authentication through the login name on the RADIUS server.

User name

User name of the PAM user account.

Login name

PAM user account login name.

Password

Password for the user account. The employee’s central password can be mapped to the user account password. For more information about an employee’s central password, see One Identity Manager Identity Management Base Module Administration Guide.

If you use a random generated initial password for the user accounts, it is automatically entered when a user account is created.

The password is deleted from the database after publishing to the target system.

NOTE: One Identity Manager password policies are taken into account when a user password is being verified. Ensure that the password policy does not violate the target system's requirements.

Confirmation

Reconfirm password.

Password never expires

Specifies whether the password expires. This option is usually used for service accounts.

Change password at next login

Specifies whether the user must change their password the next time they log in.

Domain

User account’s domain.

Require certificate authentication

Specifies whether the user can log in only with a domain-issued user certificate or SmartCard.

Certificate thumbprint (SHA-1)

Unique hash value (40 hexadecimal numbers) of the hash certificate.

Email address or name claim

Email address or name claim of the external organization’s user account.

Display name

 Display name of the PAM user account.

Last login

Time of the last login to the system.

Time zones

The user's time zone. The default time zone is UTC (Coordinated Universal Time).

Risk index (calculated)

Maximum risk index value of all assigned groups. The property is only visible if the QER | CalculateRiskIndex configuration parameter is set. For more information, see the One Identity Manager Risk Assessment Administration Guide.

Category

Categories for the inheritance of groups by the user account. Groups can be selectively inherited by user accounts. To do this, groups and user accounts or contacts are divided into categories. Select one or more categories from the menu.

Identity

User account's identity type Permitted values are:

  • Primary identity: Employee's default user account.

  • Organizational identity: Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.

  • Personalized administrator identity: User account with administrative permissions, used by one employee.

  • Sponsored identity: User account to use for a specific purpose. Training, for example.

  • Shared identity: User account with administrative permissions, used by several employees. Assign all employees that use this user account.

  • Service identity: Service account.

Groups can be inherited

Specifies whether the user account can inherit groups through the linked employee. If the option is set, the user account inherits groups through hierarchical roles, in which the employee is a member, or through IT Shop requests.

  • If you add an employee with a user account to a department, for example, and you have assigned groups to this department, the user account inherits these groups.

  • If an employee has requested group membership in the IT Shop and the request is granted approval, the employee's user account only inherits the group if the option is set.

Privileged user account

Specifies whether this is a privileged user account.

System object Identifies the user as a part of the system.
User account is disabled

Specifies whether the user account is disabled. If a user account is not required for a period of time, you can temporarily disable the user account by using the <User account is deactivated> option.

Account locked

Specifies whether the user account is locked. Depending on the configuration, the user account in the Privileged Account Management system is locked after multiple incorrect password attempts.

Created on

 Time at which the user account was created.
Created by User who created the user account.
Related topics
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação