Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Identity Manager 9.3 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics The full-text search in One Identity Manager Localization in One Identity Manager Process orchestration in One Identity Manager
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on using date values Tips for using PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Displaying messages in the user interface Referencing packages and files in scripts Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Committing and compiling script changes Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue Processor tasks Structure of the Jobservice.cfg configuration file

Using the configuration file template

NOTE: The template is only available in the Job Service Configuration program.

The SQL server direct template is supplied for configuring the One Identity Manager Service with a direct database connection.

This template already contains the most important modules with settings for a simple One Identity Manager Service configuration with a direct connection to a SQL Server. You can load the template using the menu item Templates > SQL server direct. After loading, the configuration the template needs to be modified as required.

Related topics

Selecting module types and editing parameters

The module list of the One Identity Manager Service configuration gives an overview of the individual configuration sections. A selection of module types is available for certain modules.

To select a module type

  1. Click on the module in the module list.

  2. Use Insert to open the module type drop-down.

  3. Select the module type you want from the list and insert it with the OK button.

To change the name of a module type

  1. Click on the module in the module list.

  2. Select the module type and click Rename.

  3. Change the name of the module type.

  4. Press return.

To delete a module type

  1. Click on the module in the module list.

  2. Select the module type and click Delete.

To edit a parameter value

  1. Select the parameter in the Properties column.

  2. Click Edit.

When a item is selected in the module list, all possible parameters and their values are displayed. You can change some values by clicking in input field or on the option button in the Value column.

NOTE: The parameter description in each module contains the parameter name, in brackets, which is used in the configuration file.

The following icons are used:

Table 62: Meaning of the icons for the module parameters
Icon Meaning

The value is passed as a string.

Compulsory input. The parameter must be altered as required. The value is passed as a string.

The value is passed as an integer.

The parameter can be enabled or disabled.

This parameter is added during run-time. The One Identity Manager Service does not need to be restarted.

The parameter takes effect after the One Identity Manager Service is restarted.

Related topics

Validating the configuration file

The verification test ensures that the minimum requirements for a configuration file are met.

To start the validity check in the One Identity Manager Service configuration

  • Use the button to test the configuration.

    Errors and warnings are sent to a message window.

Table 63: Verification test error output
Errors Output

No Job provider found.

Errors

No Logwriter found.

Errors

No input in compulsory field.

Errors

No Job destination found.

Warning

No plugins found.

Warning

Related topics

Configuring the MSSQLJobProvider

The MSSQLJobProvider handles One Identity Manager database process requests on a SQL Server. You configure the Job provider in the Process collection module.

Table 64: MSSQLJobProvider parameters

Parameters

Description

Max. number of pending requests (RequestQueueLimit)

The process requests are internally cached. This parameter defines the maximum number of cache entries. The default value is 1000.

Max. number of pending requests (RequestQueueLimit)

The process results are internally cached. This parameter defines the maximum number of cache entries. The default value is 10000.

Results flush timeout on shutdown in seconds (FlushTimeoutSeconds)

The service can continue to write results to the database until this timeout is reached. Input in seconds. The default value is 10 seconds.

Connection parameter (ConnectString)

Access data for the database server and the database to be used At least one user with the configuration user access level is required for process collection. Some functions may require an administrative user.

  • Server: Database server.

  • Windows authentication: (Optional) Specifies whether the integrated 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: User's SQL login name.

  • Password: Password for the SQL user's login.

  • Database: List of possible databases on the database server. Select the database.

  • Encrypt communication: Specifies whether encryption is required for exchanging data between the client and server. Select the minimum encryption level. The encryption level that is actually used depends on the database server configuration. For more information, see the documentation from Microsoft.

    Permitted values are:

    • Optional: Communication is not encrypted.

    • Mandatory: Data exchange is encrypted. The Trust server certificate option, allows you to also specify whether to verify the server certificate.

    • Strict (SQL Server 2022 and Azure SQL): The data exchange is encrypted.  The server certificate is always verified.

  • Trust server certificate: If this option is enabled, the data exchange between the client and server is encrypted. However, the server certificate is not verified.

Related topics
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation