Special synchronization cases for valid permissions
Valid permissions are mapped in the One Identity Manager database in the SPSWebAppHasPermission table; assignments of valid permissions to permission levels are mapped in the SPSRoleHasSPSPermission table.
If you remove permissions from the list of valid permissions for a web application in SharePoint, the permissions cannot be assigned to permission levels within the web application from this point on. Assignments to permission levels that already exist for these permissions remain intact but are not active. These permissions are deleted from the SPSWebAppHasPermission table during synchronization. Assignments to permission levels that already exist for these permissions are not changed. Inactive permissions are displayed in the permission levels' overview.
Related topics
Displaying synchronization results
Synchronization results are summarized in the synchronization log. You can specify the extent of the synchronization log for each system connection individually. One Identity Manager provides several reports in which the synchronization results are organized under different criteria.
To display a synchronization log
-
In the Synchronization Editor, open the synchronization project.
-
Select the Logs category.
-
Click 
in the navigation view toolbar.
Logs for all completed synchronization runs are displayed in the navigation view.
-
Select a log by double-clicking it.
An analysis of the synchronization is shown as a report. You can save the report.
To display a provisioning log
-
In the Synchronization Editor, open the synchronization project.
-
Select the Logs category.
-
Click 
in the navigation view toolbar.
Logs for all completed provisioning processes are displayed in the navigation view.
-
Select a log by double-clicking it.
An analysis of the provisioning is shown as a report. You can save the report.
The log is marked in color in the navigation view. This mark shows you the status of the synchronization/provisioning.
TIP: The logs are also displayed in the Manager under the <target system> > synchronization log category.
Synchronization logs are stored for a fixed length of time.
To modify the retention period for synchronization logs
Customizing the synchronization configuration
Having used the Synchronization Editor to set up a synchronization project for initial synchronization of a SharePoint farm, you can use the synchronization project to load SharePoint objects into the One Identity Manager database. If you manage user accounts and their authorizations with One Identity Manager, changes are provisioned in the SharePoint environment.
You must customize the synchronization configuration to be able to regularly compare the database with the SharePoint environment and to synchronize changes.
- To use One Identity Manager as the primary system during synchronization, create a workflow with synchronization in the direction of the Target system.
- You can use variables to create generally applicable synchronization configurations that contain the necessary information about the synchronization objects when synchronization starts. Variables can be implemented in base objects, schema classes, or processing methods, for example.
- Use variables to set up a synchronization project for synchronizing different farms. Store a connection parameter as a variable for logging in to the farms.
- To specify which SharePoint objects and database objects are included in synchronization, edit the scope of the target system connection and the One Identity Manager database connection. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.
- Update the schema in the synchronization project if the One Identity Manager schema or target system schema has changed. Then you can add the changes to the mapping.
IMPORTANT: As long as a synchronization process is running, you must not start another synchronization process for the same target system. This especially applies, if the same synchronization objects would be processed.
-
If another synchronization process is started with the same start up configuration, the process is stopped and is assigned Frozen status. An error message is written to the One Identity Manager Service log file.
-
Starting another synchronization process with different start up configuration that addresses same target system may lead to synchronization errors or loss of data. Specify One Identity Manager behavior in this case, in the start up configuration.
-
Use the schedule to ensure that the start up configurations are run in sequence.
-
Group start up configurations with the same start up behavior. Specify Stop on error or Postpone and wait as start up behavior.
Detailed information about this topic
How to configure SharePoint synchronization
The synchronization project for initial synchronization provides a workflow for initial loading of target system objects (initial synchronization) and one for provisioning object modifications from the One Identity Manager database to the target system (provisioning). To use One Identity Manager as the primary system during synchronization, you also require a workflow with synchronization in the direction of the Target system.
To create a synchronization configuration for synchronizing SharePoint farms
-
In the Synchronization Editor, open the synchronization project.
TIP: You can start the Synchronization Editor on any server to modify an existing synchronization project. Set up a remote connection to communicate with farm servers.
-
Check whether the existing mappings can be used to synchronize into the target system. Create new maps if required.
-
Create a new workflow with the workflow wizard.
This creates a workflow with Target system as its direction of synchronization.
-
Create a new start up configuration. Use the new workflow to do this.
- Save the changes.
-
Run a consistency check.
Detailed information about this topic
