When you start one of the One Identity Manager tools, a default connection dialog box opens.
Figure 5: Default connection dialog
When you log in, you need to be aware of the difference between a database user and a user of individual One Identity Manager tools (system user). More than one system user may work with the same database account.
Login takes place in two steps:
Permitted system user IDs are determined by the authentication module you select. The One Identity Manager provides different authentication parameters.
|
NOTE: When you start the program, it tries to restore the last used connection. This might lead to a delay resulting in an error if you frequently swap between connections to other database servers. To prevent the previous connection restoring, create the following registry key: HKEY_CURRENT_USER\Software\One Identity\One Identity Manager\Global\Settings\[RestoreLastConnection]="false" |
To select an existing connection
|
NOTE: Newly created connection are only shown in the list after the program has been restarted. |
To create a new connection to a One Identity Manager database under SQL Server
Data | Description |
---|---|
Server |
Database server. |
Windows authentication |
Specifies whether Windows authentication is used. This type of authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication. |
User |
Database user. |
Password |
Database user password. |
Database |
Database. |
This attempts to connect the database with the given connection data. You are prompted to confirm a message about the test.
|
NOTE: Use Options | Advanced options to make further changes to the database connection configuration settings. |
Click Finished.
Figure 6: Connection Data Dialog Box under SQL Server
To create a new connection to a One Identity Manager database under Oracle
Data | Description |
---|---|
Direct access (without Oracle client) | Set this option for direct access.
Deactivate this option for access via Oracle Clients. Which connection data is required, depends on how this option is set. |
Server | Database server. |
Port | Oracle instance port. |
Service name | Service name. |
User | Oracle database user. |
Password | Database user password. |
Data source | TNS alias name from TNSNames.ora. |
This attempts to connect the database with the given connection data. You are prompted to confirm a message about the test.
|
NOTE: Use Options | Advanced options to make further changes to the database connection configuration settings. |
Click Finished.
Figure 7: Connection Data Dialog Box under Oracle
To set up a new connection to the application server
This attempts to connect the database with the given connection data. You are prompted to confirm a message about the test.
|
NOTE: Use Options | Advanced options to make further changes to the database connection configuration settings. |
Figure 8: Dialog box for connecting to the application server
To delete a connection
The database connection is no longer displayed in the connection dialog.
Following the database login, the user must log in as a system user to the started program. Permitted system user IDs are determined by the authentication module you select.
To log in to One Identity Manager tools with a system user identifier
This displays a list of all available authentication modules.
Which login data you require depends on the authentication module selected.
The connection data is saved and made available for the next login.
Figure 9: Connection Dialog Box with Administration Tool Login
If you have entered a system user ID that is not supported by the selected authentication module, the following error message appears:
[810284] Failed to authenticate user.
[810015] Login for user {0} failed.
[810017] Wrong user name or password.
Repeat the login by selecting another authentication module or another system user ID.
|
NOTE: After initial schema installation, only the authentication modules "system user" and "ComponentAuthenticator" and the role-based authentication modules are enabled in the One Identity Manager. |
One Identity Manager uses different authentication modules for logging in to administration tools. Authentication modules identify the system users to be used and load the user interface and database resource editing permissions depending on their permission group memberships.
|
NOTE: After initial schema installation, only the authentication modules "system user" and "ComponentAuthenticator" and role-based authentication modules are enabled in the One Identity Manager. |
|
Note: You can log into One Identity Manager tools with all authentication modules which can be selected in the user interface and are listed in the connection dialog box. If necessary, you should ensure that users determined through the authentication module, own the required permissions to use the program. |
To enable other authentication modules
Save the changes to the database using Database | Commit to database....
This allows you to log in to the assigned application using this authentication module. Ensure that users found through the authentication module have the required permissions to use the program.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy