Chat now with support
Chat with Support

Identity Manager 9.1.3 - Authorization and Authentication Guide

About this guide One Identity Manager application roles Granting One Identity Manager schema permissions through permissions groups Managing permissions to program functions One Identity Manager authentication modules OAuth 2.0/OpenID Connect authentication Multi-factor authentication in One Identity Manager Granular permissions for the SQL Server and database Installing One Identity Redistributable STS Preventing blind SQL injection Program functions for starting the One Identity Manager tools Minimum access levels of One Identity Manager tools

Employee (dynamic)

NOTE: This authentication module is available if the Identity Management Base Module is installed.

Credentials

Employee's central user account and password.

Prerequisites

  • The employee exists in the One Identity Manager database.

  • The central user account is entered in the employee's main data.

  • The system user password is entered in the employee's main data.

  • The configuration data for dynamically determining the system user is defined in the application. Thus, an employee can, for example, be assigned a system user dynamically depending on their department membership.

Set as default

Yes

Single sign-on

No

Front-end login allowed

Yes

Web Portal login allowed

Yes

Remarks

If an employee has more than one identity, the QER | Person | MasterIdentity | UseMasterForAuthentication configuration parameter controls which employee identity is used for authentication.

  • If this configuration parameter is set, the employee’s main identity is used for authentication.

  • If this configuration parameter is not set, the employee’s subidentity is used for authentication.

The application configuration data is used to determine a system user, which is automatically assigned to the employee. The user interface and permissions are loaded through the system user that is dynamically assigned to the logged in employee.

Changes to the data are assigned to the logged in employee.

Related topics

User account

NOTE: This authentication module is available if the Identity Management Base Module is installed.

Credentials

The authentication module uses the Active Directory login data of the user currently logged in on the workstation.

Prerequisites

  • The system user with permissions exists in the One Identity Manager database.

  • The employee exists in the One Identity Manager database.

  • Permitted logins are entered in the employee's main data. The logins are expected in the form: domain\user.

  • The system user is entered in the employee's main data.

Set as default

No

Single sign-on

Yes

Front-end login allowed

Yes

Web Portal login allowed

Yes

Remarks

All employee logins saved in the One Identity Manager database are found. The employee whose login data matches that of the current user is used for logging in.

If an employee has more than one identity, the QER | Person | MasterIdentity | UseMasterForAuthentication configuration parameter controls which employee identity is used for authentication.

  • If this configuration parameter is set, the employee’s main identity is used for authentication.

  • If this configuration parameter is not set, the employee’s subidentity is used for authentication.

The user interface and permissions are loaded through the system user that is directly assigned to the employee found.

Data modifications are attributed to the current user account.

User account (role-based)

NOTE: This authentication module is available if the Identity Management Base Module is installed.

Credentials

The authentication module uses the Active Directory login data of the user currently logged in on the workstation.

Prerequisites

  • The employee exists in the One Identity Manager database.

  • Permitted logins are entered in the employee's main data. The logins are expected in the form: domain\user.

  • The employee is assigned at least one application role.

Set as default

No

Single sign-on

Yes

Front-end login allowed

Yes

Web Portal login allowed

Yes

Remarks

All employee logins saved in the One Identity Manager database are found. The employee whose login data matches that of the current user is used for logging in.

If an employee has more than one identity, the QER | Person | MasterIdentity | UseMasterForAuthentication configuration parameter controls which employee identity is used for authentication.

  • If this configuration parameter is set, the employee’s main identity is used for authentication.

  • If this configuration parameter is not set, the employee’s subidentity is used for authentication.

A dynamic system user is determined from the employee's application roles. The user interface and the permissions are loaded through this system user.

Data modifications are attributed to the current user account.

User account (manual input/role-based)

NOTE: This authentication module is available if the Identity Management Base Module is installed.

Credentials

Login name and password for registering with Active Directory. You do not have to enter the domain.

Prerequisites

  • The employee exists in the One Identity Manager database.

  • Permitted logins are entered in the employee's main data. The logins are expected in the form: domain\user.

  • The employee is assigned at least one application role.

  • Domains permitted for login are entered in the TargetSystem | ADS | AuthenticationDomains configuration parameter.

    NOTE: This configuration parameter is available if the Active Directory Module is installed.

Set as default

Yes

Single sign-on

No

Front-end login allowed

Yes

Web Portal login allowed

Yes

Remarks

All employee logins saved in the One Identity Manager database are found. The employee whose login data matches that of the current user is used for logging in. This takes into account the list of permitted Active Directory domains.

If an employee has more than one identity, the QER | Person | MasterIdentity | UseMasterForAuthentication configuration parameter controls which employee identity is used for authentication.

  • If this configuration parameter is set, the employee’s main identity is used for authentication.

  • If this configuration parameter is not set, the employee’s subidentity is used for authentication.

A dynamic system user is determined from the employee's application roles. The user interface and the permissions are loaded through this system user.

Data modifications are attributed to the current user account.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating