サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.0 LTS - 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

Password reset (role-based)

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

The authentication module is used for login to Password Reset Portal. The authentication module checks the passcode or the employee’s answers to the password questions. In the case of login with an passcode, this information is deleted after a successful login.

Credentials

Central user account and passcode.

- OR -

Central user account and answers to the password questions.

- OR -

Target system user account and passcode.

- OR -

Target system user account and answers to password questions.

Prerequisites

  • The employee exists in the One Identity Manager database.

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

  • Using the target system user account: The user account exists in the One Identity Manager database and the employee is entered in the main data of the employee’s user account.

  • The employee is not deactivated or has the certification status New.

  • The employee has an passcode or the questions and answers for the password prompt have been specified.

  • The employee is assigned at least one application role.

Set as default

Yes

Single sign-on

No

Front-end login allowed

No

Web Portal login allowed

No

Remarks

The application token for Password Reset Portal must be specified. You set the application token when installing Password Reset Portal. The application token is saved as a hash value in the database in the QER | Person | PasswordResetAuthenticator | ApplicationToken parameter and stored encrypted in the web.config file. For more information about configuring the Password Reset Portal, see the One Identity Manager Web Application Configuration Guide.

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

In the Designer, modify the following configuration parameters so that target system accounts can be used for logging in. If the configuration parameters are not set, the employee’s central user account is used.

Table 32: Configuration parameters for the authentication module
Configuration parameter Meaning

QER | Person | PasswordResetAuthenticator | SearchTable

Table in the One Identity Manager schema which stores the user information. The table must contain a foreign key with the name UID_Person (or CCC_UID_Person) that references the Person table.

Example: ADSAccount

QER | Person | PasswordResetAuthenticator | SearchColumn

Pipe (|) delimited list of columns from the One Identity Manager table (SearchTable) used to search for the user name of the logged in user.

Example: CN|SamAccountName

NOTE: The QBMSplittedLookup table can be used as a lookup table. SplittedElement can be used as a search column.

QER | Person | PasswordResetAuthenticator | EnabledBy

Pipe (|) delimited list of Boolean columns from the One Identity Manager table (SearchTable) enabled by the user account for the login.

QER | Person | PasswordResetAuthenticator | DisabledBy

Pipe (|) delimited list of Boolean columns from the One Identity Manager table (SearchTable) disabled by the user account for the login.

Example: AccountDisabled

Decentralized identity

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

The authentication module can be used to log in using a decentralized identity.

Credentials

The employee's email address and decentralized identity.

Prerequisites

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

  • The employee exists in the One Identity Manager database.

  • The decentralized identity is entered in the employee main data.

  • The default email address or the contact email address is in the employee's main data.

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

Set as default

No

Single sign-on

No

Front-end login allowed

Yes

Web Portal login allowed

Yes

Remarks

To identify the employee, the email address provided during login is verified against the default email address and the contact email address.

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 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 logged in employee.

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

Decentralized Identity (role-based)

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

The authentication module can be used to log in using a decentralized identity.

Credentials

The employee's email address and decentralized identity.

Prerequisites

  • The employee exists in the One Identity Manager database.

  • The decentralized identity is entered in the employee main data.

  • The default email address or the contact email address is in the employee's main data.

  • The employee is assigned at least one application role.

Set as default

No

Single sign-on

No

Front-end login allowed

Yes

Web Portal login allowed

Yes

Remarks

To identify the employee, the email address provided during login is verified against the default email address and the contact email address.

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 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.

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

Editing authentication modules

Before you can use an authentication module for logging on, the following prerequisites must be fulfilled:

  1. The authentication module must be enabled.

  2. The authentication module must be assigned to the application.

  3. The assignment of the authentication module to the application must be enabled.

This allows you to log in to the assigned application using this authentication module. Ensure that users found through the authentication module also have the required program function to use the program.

Detailed information about this topic
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択