Configuring Memberships Provisioning

Configuring Memberships Provisioning

Memberships, for example, user accounts in groups, are saved in assignment tables in the One Identity Manager database. During provisioning of modified memberships, changes made in the target system will probably be overwritten. This behavior can occur under the following conditions:

• Memberships are saved in the target system as an object property in list form (Example: List of user accounts in the property Users of an SPGroup).
• Memberships can be modified in either of the connected systems.
• A provisioning workflow and provisioning processes are set up.

If a membership in One Identity Manager changes, the complete list of members is transferred to the target system by default. Memberships, previously added to the target system are removed by this; previously deleted memberships are added again.

To prevent this, provisioning can be configured such that only the modified membership is provisioned in the target system. The corresponding behavior is configured separately for each assignment table.

To allow separate provisioning of memberships

1. Start the Manager.
2. Select the category SharePoint | Basic configuration data | Target system types.
3. Select Configure tables for publishing.
4. Select the assignment tables for which you want to allow separate provisioning. Multi-select is possible.
   • The option can only be set for assignment tables whose base table has a column XDateSubItem.
   • Assignment tables, which are grouped together in a virtual schema property in the mapping, must be labeled identically (for example SPSGroupHasSPSRLAsgn and SPSUserHasSPSRLAsgn).
5. Click Enable merging.
6. Save the changes.

For each assignment table labeled like this, the changes made in the One Identity Manager are saved in a separate table. During modification provisioning, the members list in the target system is compared to the entries in this table. This means that only modified memberships are provisioned and the members list does not get entirely overwritten.

For more detailed information about provisioning memberships, see the One Identity Manager Target SystemAn instance of a target system in which the employees managed by One Identity Manager have access to network resources. Example: An Active Directory domain X for target system type "Active Directory", a directory Y for target system type "LDAP", a client Z for target system type "SAP R/3". SynchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. Reference Guide.

Supporting Analysis of Synchronization Issues

Help for Analyzing Synchronization Issues

You can generate a report for analyzing problems which occur during synchronization, for example, insufficient performance. The report contains information such as:

• Consistency check results
• Revision filterFilters all system objects not changed since the last synchronization. The deciding factor being the revision property modification. SynchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. can be speeded up with revision filtering. settings
• ScopeSection of a connected system which should be synchronized. The scope is defined with a filter. applied
• Analysis of the synchronization buffer
• Object access times in the One Identity Manager database and in the target system

To generate a synchronization analysis report

1. Open the synchronization project in the Synchronization EditorOne Identity Manager tool for configuring target system synchronization..

2. Select the menu Help | Generate synchronization analysis report and answer the security prompt with Yes.

   The report may take a few minutes to generate. It is displayed in a separate window.

3. Print the report or save it in one of the available output formats.

Deactivating Synchronization

Deactivating Synchronization

Regular synchronization cannot be started until the synchronization project and the schedule are active.

To prevent regular synchronization

• Select the start up configuration and deactivate the configured schedule.

  Now you can only start synchronization manually.

An activated synchronization project can only be edited to a limited extend. The schema in the synchronization project must be updated if schema modifications are required. The synchronization project is deactivated in this case and can be edited again.

Furthermore, the synchronization project must be deactivated if synchronization should not be started by any means (not even manually).

To deactivate the loaded synchronization project

1. Select General on the start page.
2. Click Deactivate project.

Detailed information about this topic

• Creating a Synchronization Project for initial Synchronization of a SharePoint Farm

Basic Data for Managing SharePoint

Base Data for Managing SharePoint

The following data is relevant for managing a SharePoint environment 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. You can find an overview of all configuration parameters in the category Base data | General | Configuration parameters in the Designer.

  For more information, see Appendix: Configuration Parameters for Managing SharePoint.

• 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 have a user account in the target system, a new user account is created. This is done by assigning account definitions to an employee using the integrated inheritance mechanism followed by process handling.

  For more information, see Setting Up Account Definitions.

• Authentication Modes

  One Identity Manager supports claims-based authentication as well as classical Windows authentication for logging on to the SharePoint server. The authentication mode to use is stored with the web applications and the user accounts. Usable authentication modes are maintained in the One Identity Manager database.

  For more information, see Authentication Modes.

• Prefixes

  Prefixes are URLs relative to a web application that can be stored under a site collection.

  For more information, see Prefixes.

• Zones and Alternative URLs

  All the zones that you can configure for a web application are stored in the One Identity Manager database.

  For more information, see Zones and Alternative URLs.

• Site templates

  Use site templates to add sites.

  For more information, see SharePoint Site Templates.

• Permissions

  User permissions for a SharePoint site or a web application are authorized by SharePoint permissions. Permissions are grouped into permission levels and permission policies.

  For more information, see SharePoint Permissions.

• Target system types

  Target system types are required for configuring target system comparisons. Tables containing outstanding objects are maintained on target system types.

  For more information, see Post-Processing Outstanding Objects.

• Server

  In order to handle SharePoint specific processes in One Identity Manager, the synchronization server and its server functionality must be declared.

  For more information, see Editing a Server.

• Target system managers

  A default application role exists for the target system manager in the One Identity Manager. Assign this application to employees who are authorized to edit the SharePoint farms in One Identity Manager.

  Define other application roles, if you want to limit target system managers' access permissions to individual SharePoint farms. The application roles must be added under the default application role.

  For more information, see Target System Managers.