Ignoring data error in synchronization
By default, objects with incorrect data are not synchronized. These objects can be synchronized once the data has been corrected. In certain situations, however, it might be necessary to synchronize objects like these and ignore the data properties that have errors. This synchronization behavior can be configured in One Identity Manager.
To ignoring data errors during synchronization in One Identity Manager
-
In the Synchronization Editor, open the synchronization project.
-
Select the Configuration > One Identity Manager connection category.
-
In the General view, click Edit connection.
This starts the system connection wizard.
-
On the Additional options page, enable Try to ignore data errors.
This option is only effective if Continue on error is set in the synchronization workflow.
Default columns, such as primary keys, UID columns, or mandatory input columns cannot be ignored.
- Save the changes.
IMPORTANT: If this option is set, One Identity Manager tries to ignore commit errors that could be related to data errors in a single column. This causes the data changed in the affected column to be discarded and the object is subsequently saved again. This effects performance and leads to loss of data.
Only set this option in the exceptional circumstance of not being able to correct the data before synchronization.
Pausing handling of target system specific processes (Offline mode)
If a target system connector is not able to reach the target system temporarily, you can enable offline mode for the target system. This stops target system specific processes from being frozen and having to be manually re-enabled later.
Whether offline mode is generally available for a target system connection is set in the base object of the respective synchronization project. Once a target system is truly unavailable, the target system connection can be switched offline and online again with the Launchpad.
In offline mode, all Job servers assigned to the base object are stopped. This includes the synchronization server and all Job servers involved in load balancing. If one of the Job servers also handles other tasks, these are not processed either.
Prerequisites
Offline mode can only be specified for a base object if certain prerequisites are fulfilled.
-
The synchronization server is not used for any other base object as a synchronization server.
-
If a server function is assigned to the base object, none of the Job servers with this server function may have any other server function (for example, update server).
-
A dedicated synchronization server must be set up to exclusively process the Job queue for this base object. The same applies to all Job servers that are determined by the server function.
To allow offline mode for a base object
-
In the Synchronization Editor, open the synchronization project.
-
Select the Base objects category.
-
Select a base object in the document view and click 
.
-
Enable Offline mode available.
- Click OK.
- Save the changes.
IMPORTANT: To prevent data inconsistencies, the offline phase should be kept as short as possible.
The number of processes to handle depends on the extent of the changes in the One Identity Manager database and their effect on the target system during the offline phase. To establish data consistency between the One Identity Manager database and the target system, all pending processes must be handled before synchronization can start.
Only use offline mode, if possible, for short system downtimes such as maintenance windows.
To flag a target system as offline
-
Start the Launchpad and log in on the One Identity Manager database.
-
Select Manage > System monitoring > Flag target systems as offline.
-
Click Run.
This opens the Manage offline systems dialog. The Base objects section displays the base objects of target system connections that can be switched to offline.
-
Select the base object whose target system connection is not available.
-
Click Switch offline.
- Confirm the security prompt with OK.
This stops all the Job servers assigned to the base object. No more synchronization or provisioning Jobs are performed. The Job Queue Info program shows when a Job server has been switched offline and the corresponding tasks are not being processed.
For more information about offline mode, see the One Identity Manager Target System Synchronization Reference Guide.
Related topics
Managing Google Workspace user accounts and employees
The main feature of One Identity Manager is to map employees together with the main data and permissions available to them in different target systems. To achieve this, information about user accounts and permissions can be read from the target system into the One Identity Manager database and linked to employees. This provides an overview of the permissions for each employee in all of the connected target systems. One Identity Manager offers the option of managing user accounts and their permissions. You can provision modifications in the target systems. Employees are supplied with the necessary permissions in the connected target systems according to their function in the company. Regular synchronization keeps data consistent between target systems and the One Identity Manager database.
Because requirements vary between companies, One Identity Manager offers different methods for supplying user accounts to employees. One Identity Manager supports the following methods for linking employees and their user accounts:
-
Employees can automatically obtain their account definitions using user account resources.
If an employee does not yet have a user account in a customer, a new user account is created. This is done by assigning account definitions to an employee using the integrated inheritance mechanisms and subsequent process handling.
When you manage account definitions through user accounts, you can specify the way user accounts behave when employees are enabled or deleted.
-
When user accounts are inserted, they can be automatically assigned to an existing employee or a new employee can be created if necessary. In the process, the employee main data is created on the basis of existing user account main data. This mechanism can be implemented if a new user account is created manually or by synchronization. However, this is not the One Identity Manager default method. You must define criteria for finding employees for automatic employee assignment.
-
Employees and user accounts can be entered manually and assigned to each other.
For more information about employee handling and administration, see the One Identity Manager Target System Base Module Administration Guide.
Related topics
Account definitions for Google Workspace user accounts
One Identity Manager has account definitions for automatically allocating user accounts to employees. 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 employees must have 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.
Specify the manage level for an account definition for managing user accounts. The user account’s manage level specifies the extent of the employee’s properties that are inherited by the user account. This allows an employee to have several user accounts in one target system, for example:
For more detailed information about the principles of account definitions, manage levels, and determining the valid IT operating data, see the One Identity Manager Target System Base Module Administration Guide.
The following steps are required to implement an account definition:
-
Creating account definitions
-
Configuring manage levels
-
Creating the formatting rules for IT operating data
-
Collecting IT operating data
-
Assigning account definitions to employees and target systems
Detailed information about this topic
