To post-process outstanding objects, assign the custom target system's target system type to tables, which can contain outstanding objects. Specify the tables for which outstanding objects can be published in the target system during post-processing.
To add tables to target system synchronization
-
In the Manager, select the Custom target systems | Basic configuration data | Target system types category.
-
In the result list, select the custom target system's target system type.
-
Select the Assign synchronization tables task.
-
In the pane, assign custom tables to the outstanding objects you want to handle.
- Save the changes.
-
Select the Configure tables for publishing task.
-
Select the tables that contain the outstanding objects that can be published in the target system and set the Publishable option.
- Save the changes.
To publish outstanding objects
- For each table you want to publish outstanding objects for, create a process that is triggered by the HandleOutstanding event and runs provisioning of the objects. Use the AdHocProjection process task of the ProjectorComponent process component. For detailed information about defining processes, see the One Identity Manager Configuration Guide.
NOTE: You must set up matching processes in One Identity Manager to publish outstanding objects that are being post-processed. For more information, see Setting up script-controlled data provisioning in a custom target system.
If you use the CSV connector for provisioning, ensure that the CSV connector has write access to the CSV files. That means, the Connection is read-only option must not be set for the target system connection. For more detailed information, see the One Identity Manager Target System Synchronization Reference Guide.
To post-process outstanding objects
- Select the Custom target systems | Basic configuration data | Target system synchronization: <Target system> category.
In the navigation view, all tables assigned to the target system type are displayed.
- Select the table whose outstanding objects you want to edit in the navigation view.
All objects marked as outstanding are shown on the form.
TIP:
To display object properties of an outstanding object
- Select the object on the target system synchronization form.
- Open the context menu and click Show object.
-
Select the objects you want to rework. Multi-select is possible.
-
Click on one of the following icons in the form toolbar to execute the respective method.
Table 5: Methods for handling outstanding objects
|
|
Delete |
The object is immediately deleted from the One Identity Manager database. Deferred deletion is not taken into account. The Outstanding label is removed from the object.
Indirect memberships cannot be deleted. |
|
|
Publish |
The object is added to the target system. The Outstanding label is removed from the object.
The method triggers the HandleOutstanding event. This runs a target system specific process that triggers the provisioning process for the object.
Prerequisites:
|
|
|
Reset |
The Outstanding label is removed for the object. |
- Confirm the security prompt with Yes.
NOTE: By default, the selected objects are processed in parallel, which speeds up execution of the selected method. If an error occurs during processing, the action is stopped and all changes are discarded.
Bulk processing of objects must be disabled if errors are to be localized, which means the objects are processed sequentially. Failed objects are named in the error message. All changes that were made up until the error occurred are saved.
To disable bulk processing
Related topics
The following base data is relevant for managing a custom target system in One Identity Manager.
- Configuration parameter
Use configuration parameters to configure the behavior of the system's basic settings. One Identity Manager provides default settings for different configuration parameters. Check the configuration parameters and modify them as necessary to suit your requirements.
Configuration parameters are defined in the One Identity Manager modules. Each One Identity Manager module can also install configuration parameters. In the Designer, you can find an overview of all configuration parameters in the Base data | General | Configuration parameters category.
For more information, see Configuration parameters for managing custom target systems.
- Account definitions
One Identity Manager has account definitions for automatically allocating user accounts to employees during working hours. You can create account definitions for every target system. If an employee does not yet have a user account in a target system, a new user account is created. This is done by assigning account definitions to an employee.
For more information, see Setting up account definitions.
- Password policy
provides you with support for creating complex password policies, for example, for system user passwords, the employees' central password as well as passwords for individual target systems. Password polices apply not only when the user enters a password but also when random passwords are generated.
Predefined password policies are supplied with the default installation that you can use or customize if required. You can also define your own password policies.
For more information, see Password policies for user accounts.
- Initial password for new user accounts
You have the different options for issuing an initial password for user accounts. The central password of the assigned employee can be aligned with the user account password, a predefined, fixed password can be used, or a randomly generated initial password can be issued.
For more information, see Initial password for new user accounts.
- Email notifications about credentials
When a new user account is created, the login data are sent to a specified recipient. In this case, two messages are sent with the user name and the initial password. Mail templates are used to generate the messages.
For more information, see Email notifications about login data.
- Server
A server on which One Identity Manager Service is installed configured and started must be provided to provision data from One Identity Manager into a custom target system using synchronization by script. The server must be declared in One Identity Manager and entered as the synchronization server in the target system. For more information, see Setting up a server for data provisioning to a custom target system.
- Target system managers
A default application role exists for the target system manager in One Identity Manager. Assign the employees who are authorized to edit all target systems in One Identity Manager to this application role.
Define additional application roles if you want to limit the edit permissions for target system managers to individual target systems. The application roles must be added under the default application role.
For more information, see Target system managers.
- Target system types
Target system types for groups custom target systems. You can assign user accounts to groups belonging to different target systems within a target system type. For more information, see Target system types.
-
Custom schema extensions to base tables
You can display custom columns in tables UNSAccountB, UNSContainerB, UNSGroupB, UNSItemB and UNSRootB in the Manager. To do this, modify the custom column's column definition. For more information, see Displaying custom schema extensions for custom target systems.
One Identity Manager has account definitions for automatically allocating user accounts to employees during working hours. You can create account definitions for every target system. If an employee does not yet have a user account in a target system, a new user account is created. This is done by assigning account definitions to an employee.
The data for the user accounts in the respective target system comes from the basic employee data. The employee must own a central user account. The assignment of the IT operating data to the employee’s user account is controlled through the primary assignment of the employee to a location, a department, a cost center, or a business role. Processing is done through templates. There are predefined templates for determining the data required for user accounts included in the default installation. You can customize templates as required.
For more details about the basics, see the One Identity Manager Target System Base Module Administration Guide.
The following steps are required to implement an account definition:
to disable bulk processing.