Identity Manager 9.2.1 - Administration Guide for Connecting to LDAP

The One Identity Manager Service must be installed on the synchronization server with the LDAP connector. The synchronization server must be declared as a Job server in One Identity Manager.

Table 3: Properties of the Job server
Property	Value
Server function	LDAP connector
Machine role	Server \| Job Server \| LDAP directories

NOTE: If several target system environments of the same type are synchronized under the same synchronization server, it is recommended that you set up a Job server for each target system for performance reasons. This avoids unnecessary swapping of connections to target systems because a Job server only has to process tasks of the same type (re-use of existing connections).

To set up a Job server, perform the following steps.

Create a Job server and install and configure the One Identity Manager Service.

Use the One Identity Manager Service to install the Server Installer. The program runs the following steps:
- Sets up a Job server.
- Specifies machine roles and server function for the Job server.
- Installs One Identity Manager Service components corresponding to the machine roles.
- Configures the One Identity Manager Service.
- Starts the One Identity Manager Service.
Use the Server Installer to install the One Identity Manager Service locally or remotely.

To remotely install the One Identity Manager Service, provide an administrative workstation on which the One Identity Manager components are installed. Ensure that the One Identity Manager components are installed on the server before installing locally. For more information about installing One Identity Manager components, see the One Identity Manager Installation Guide.
If you are working with an encrypted One Identity Manager database, declare the database key in the One Identity Manager Service. For more information about working with an encrypted One Identity Manager database, see the One Identity Manager Installation Guide.
To generate processes for the Job server, you need the provider, connection parameters and the authentication data. By default, this information is determined from the database connection data. If the Job server runs through an application server, you must configure extra connection data in the Designer. For more information about connection data, see the One Identity Manager Configuration Guide.

To install and configure the One Identity Manager Service on a server

Start the Server Installer program.

NOTE: To install remotely, start the Server Installer program on your administrative workstation. To install locally, start the program on the server.

On the Database connection page, enter the valid connection credentials for the One Identity Manager database.

You can connect via the application server or directly to connect to the database.
On the Server properties page, specify the server on which you want to install the One Identity Manager Service.
1. Select a Job server from the Server menu.
  
  - OR -
  
  To create a new Job server, click Add.
2. Enter the following data for the Job server.
  - Server: Name of the Job server.
  - Queue: Name of the queue to handle the process steps. Each Job server within the network must have a unique queue identifier. The process steps are requested by the Job queue using this exact queue name. The queue identifier is entered in the One Identity Manager Service configuration file.
  - Full server name: Full server name in accordance with DNS syntax.
    
    Syntax:
    
    <Name of servers>.<Fully qualified domain name>
  NOTE: You can use the Extended option to make changes to other properties for the Job server. You can also edit the properties later with the Designer.

On the Machine roles page, select LDAP directories.
On the Server functions page, select LDAP connector.
On the Service Settings page, enter the connection data and check the One Identity Manager Service configuration.

NOTE: The initial service configuration is predefined. If further changes need to be made to the configuration, you can do this later with the Designer. For more information about configuring the service, see the One Identity Manager Configuration Guide.

For a direct connection to the database:
1. In the module list, select Process collection > sqlprovider.
2. Click the Connection parameter entry, then click the Edit button.
3. Enter the connection data for the One Identity Manager database.
4. Click OK.
For a connection to the application server:
1. In the module list, select the Process collection entry and click the Insert button.
2. Select AppServerJobProvider and click OK.
3. In the module list, select Process collection > AppServerJobProvider.
4. Click the Connection parameter entry, then click the Edit button.
5. Enter the address (URL) for the application server and click OK.
6. Click the Authentication data entry and click the Edit button.
7. In the Authentication method dialog, select the authentication module for logging in. Depending on the authentication module, other data may be required, such as user and password. For more information about One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide.
8. Click OK.
To configure the installation, click Next.

Confirm the security prompt with Yes.
On the Select installation source page, select the directory with the install files. Change the directory if necessary.
On the Service access page, enter the service's installation data.
- Computer: Select the server, on which you want to install and start the service, from the menu or enter the server's name or IP address.
  
  To run the installation locally, select Local installation from the menu.
- Service account: Enter the details of the user account that the One Identity Manager Service is running under. Enter the user account, the user account's password and password confirmation.
The service is installed using the user account with which you are logged in to the administrative workstation. If you want to use another user account for installing the service, you can enter it in the advanced options.

You can also change the One Identity Manager Service details, such as the installation directory, name, display name, and the One Identity Manager Service description, using the advanced options.
Click Next to start installing the service.

Installation of the service occurs automatically and may take some time.
Click Finish on the last page of the Server Installer.

NOTE: In a default installation, the service is entered in the server’s service management with the name One Identity Manager Service.

Table 4: Information required for setting up a synchronization project
Data	Explanation
LDAP server's DNS name	IP address or full name of the LDAP server for connecting to the synchronization server to provide access to LDAP objects. Syntax: <Name of servers>.<Fully qualified domain name>
Authentication type	Authentication type for establishing a connection to the target system. Authentication type Basic is taken as default. For more information about authentication types, see the MSDN Library.
Communications port on the server	LDAP default communications port is 389.
User account and password for domain login	User account and password for domain login. This user account is used to access the domain. Make a user account available with sufficient permissions. For more information, see Users and permissions for synchronizing with LDAP.
Synchronization server for LDAP	All One Identity Manager Service actions are run against the target system environment on the synchronization server. Data entries required for synchronization and administration with the One Identity Manager database are processed by the synchronization server. The One Identity Manager Service with the LDAP connector must be installed on the synchronization server. The synchronization server must be declared as a Job server in One Identity Manager. Use the following properties when you set up the Job server. Server function: LDAP connector Machine role: Server \| Job Server \| LDAP directories For more information, see Setting up the LDAP synchronization server.
One Identity Manager database connection data	Database server Database name SQL Server login and password Specifies whether integrated Windows authentication is used Use of the integrated Windows authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication.
Remote connection server	To configure synchronization with a target system, One Identity Manager must load the data from the target system. One Identity Manager communicates directly with the target system to do this. Sometimes direct access from the workstation, on which the Synchronization Editor is installed, is not possible. For example, because of the firewall configuration or the workstation does not fulfill the necessary hardware and software requirements. If direct access is not possible from the workstation, you can set up a remote connection. Remote connection server configuration: One Identity Manager Service is started RemoteConnectPlugin is installed and an authentication method is set up LDAP connector is installed The remote connection server must be declared as a Job server in One Identity Manager. The Job server name is required. TIP: The remote connection server requires the same configuration as the synchronization server (with regard to the installed software and entitlements). Use the synchronization server as remote connection server as well by installing the RemoteConnectPlugin. For more detailed information about setting up a remote connection, see the One Identity Manager Target System Synchronization Reference Guide.

NOTE: The following sequence describes how to configure a synchronization project if the Synchronization Editor is both:

Run in default mode
Started from the Launchpad

If you run the project wizard in expert mode or directly from the Synchronization Editor, additional configuration settings can be made. Follow the project wizard instructions through these steps.

NOTE: Just one synchronization project can be created per target system and default project template used.

To set up an initial synchronization project for an LDAP domain

Start the Launchpad and log in on the One Identity Manager database.

NOTE: If synchronization is run by an application server, connect the database through the application server.
Select the Target system type LDAP entry and click Start.

This starts the Synchronization Editor's project wizard.

On the Choose target system page, select LDAP connector (version 2).

On the wizard's start page, click Next.
On the System access page, specify how One Identity Manager can access the target system.
- If access is possible from the workstation on which you started the Synchronization Editor, do not change any settings.
- If access is not possible from the workstation on which you started the Synchronization Editor, you can set up a remote connection.
  
  Select the Connect using remote connection server and enter the remote connection properties.
  Remote connection properties
  - Access parameters
    
    Server: Full server name or IP address of the server.
    
    To select an existing Job server as the remote connection server, click and select the server from the menu. This displays all the Job servers that have the One Identity Manager Service installed server function selected.
    
    Port: Port that is configured for the RemoteConnectPlugin.
  - Authentication
    
    If SecretAuthentication is configured for the RemoteConnectPlugin:
    
    Secret: Secret used by the Synchronization Editor to authenticate on the RemoteConnectPlugin.
    
    If ADGroupAuthentication is configured for the RemoteConnectPlugin, no data is required.
  - Options
    
    Request timeout: Maximum time allowed for a server query in seconds. If the time is exceeded, the request is canceled.
    
    Accept self-signed certificates: Specifies whether self-signed certificates can be accepted.

On the Connection credentials page, enter the connection data for accessing the LDAP system. An attempt is then made to connect to establish a connection to the server.
- Server: IP address or full name of the LDAP server for connecting to the synchronization server to provide access to LDAP objects
- Port: Communications port on the server. The LDAP default communications port is 389.
- Authentication method: Select the authentication type for logging in to the LDAP system. The following are permitted:
  - Basic: Uses default authentication.
  - Negotiate: Uses Negotiate authentication from Microsoft.
  - Anonymous: Establishes a connection without passing login credentials.
  - Kerberos: Uses Kerberos authentication.
  - NTLM: Uses Windows NT Challenge/Response (NTLM) authentication.
  - External: Uses certificate-based authentication as the external method.
  Depending on the selected authentication method, additional information may be required for logging in.
  - User name: Name of the user account for logging in to LDAP.
  - Password: Password for the user account.
  - Enable sealing: Set this option if the selected authentication method supports sealing (Sealing).
  - Enable signing: Set this option if the selected authentication method supports signing (Signing).
  - Client certificate: Select a client certificate. The certificates are determined from the user certificates (Current user certificate store) on the currently connected host. This is either the local computer that the Synchronization Editor was started on or the Job server used for connecting remotely.
    
    NOTE: Ensure that the selected certificate is also installed on all Job servers that will connect to the LDAP system.
    
    TIP: By clicking next to the field, you can display additional information about the selected certificate, for example, subject, certification authority and validity period.
- Encryption: Specify encryption for the connection. You have the following options:
  - None: No encryption is used.
  - SSL: An SSL/TLS encrypted connection is used.
  - StartTLS: StartTLS is used for encryption.
- Server certificate verification: The server certificate is checked during SSL or StartTLS encryption.
  
  NOTE: The server certificate must be valid. The root certification authority’s certificate must be the computer certificate ( Local Computer certificate store) either on the host that the Synchronization Editor was started on or on the Job server connected remotely. Ensure that the certificate is also installed on all Job servers that will connect to the LDAP system.
- Protocol version: Version of the LDAP protocol. The default value is 3.
On the Select the schema source page, select the source to provide the schema information. You have the following options:
- Load schema from LDAP Server: The schema is loaded from the LDAP. (Default)
- Load schema from given LDIF string: If the LDAP server’s schema is not available, you can give an alternative source.
Load the LDAP server’s schema (default)
To load the server’s schema (default)
1. In the Source menu, select Load schema from LDAP Server.
2. (Optional) Click .
3. (Optional) To check the schema, click .
  
  Errors that are found during analysis of the schema are displayed in the Schema parsing errors pane.
Load schema from given LDIF string
To load a schema from an LDIF string
1. In the Source menu, select Load schema from given LDIF string.
2. In the Identifier field, enter a name for the schema source.
3. Insert the schema definition straight into the field.
  
  - OR -
  
  Click and select the file containing the schema.
4. To check the schema, click .
  
  Errors that are found during analysis of the schema are displayed in the Schema parsing errors pane. If you double-click on an error message, you jump to the corresponding place in the schema.
On the Select configuration preset page, specify how the connector is preconfigured. A configuration is already suggested based on the known server. Alternatively, you can enter the configuration manually. In this case, configure the setting for search queries, object changes, and object deletion.
- Use preset: Enable this option if you want to use the configuration provided for the connector. A configuration is already suggested based on the known LDAP system. You have the following options:
  - OpenDJ
  - Oracle DSEE
  - Microsoft AD LDS or Active Directory
  - Novell/NetIQ eDirectory
- Configure manually: Enable this option if you want to create the configuration manually. In this case, additional pages are offered on which you can specify the settings for search queries, object changes, and object deletion.
  Setting configuration manually
  1. On the Search settings page, set the options for LDAP search queries.
    
    The search function are structured hierarchically and are run in the order of configuration. Each search function is applied to the result of the previous search. The following search functions are available:
    
    Default Searcher: Default search settings.
    
    Use paged search: Specifies whether LDAP objects are loaded by page. This information is automatically queried through the selected preconfiguration or from the LDAP server. If the option is enabled, enter the page size.
    
    Page size: Enter the maximum number of objects to load per page. (Default 500)
    
    Remove spaces in distinguished names: Removes all spaces in distinguished name objects that, according to RFC, are not allowed or non-significant.
    
    If the function does not exist, according to RFC, all spaces that are non allowed or non-significant are not removed from the distinguished name and can cause errors in certain circumstances.
    
    AD (LDS) Search implementation: Additional search settings for Active Directory Lightweight Directory Service.
    
    Chunk size: If attributes with a large number of value are returned from a Microsoft based LDAP server, the server only sends a certain number of values back (normally 1500.) To query all the values, several queries with a scope limit are sent.
    
    The chunk size determines how many value are return per query. If the select chunk size is larger than the maximum size that the server can process, it is adjusted automatically.
    
    Enter the valid sizes: (Default 1000)
    
    Adding, editing, or deleting search functions
    
    To add a search function
    
    In the Search settings pane, click .
    
    In the menu, select the search function and click .
    
    Change the order of the search functions using and .
    
    To edit a search function
    
    In the Search settings pane, select the search function and edit the configuration in the detailed view.
    
    To delete a search function
    
    In the Search settings pane, select the search function and click .
  2. On the Modify settings page, set additional options to modify the objects. The following options are available:
    
    Default Modify implementation: Default implementation for modifying objects.
    
    Tolerate 'Attribute already exists' and 'no such attribute' and retry: Use this function to tolerate existing or missing attributes in the LDAP system when an object is changed, for example, updating group memberships. (Default)
    
    If this function is not available, changes to objects that affect existing or missing attribute in the LDAP system can cause errors.
    
    Adding or deleting modify settings
    
    To add functions
    
    In the Modify settings pane, click .
    
    In the menu, select the function and click .
    
    To delete a function
    
    In the Modify settings pane, select the function and click .
  3. On the Delete settings page, set additional options for deleting objects. The following options are available:
    
    Default delete implementation: Default configuration for deleting objects.
    
    Use DeleteTree control when deleting entries: Specifies whether the LDAP server sends the DeleteTree control to delete entries with sub-entries during deletion. This information is automatically queried through the selected preconfiguration or from the LDAP server.
    
    Editing delete settings
    
    To edit a function
    
    In the Delete settings pane, select the function and edit the configuration in the detailed view.
On the LDAP schema extensions page, configure additional schema functions that are run while the schema is being loaded.

Schema functions are structured hierarchically. A schema function is always applied to its parent schema function. The connection processes schema functions hierarchically top-down. The following schema functions are available:
- Load schema from LDAP Server/Load schema for LDIF string: Source for determining the schema.
- Return operational attributes: This schema function specifies, which attributes are additionally found for the LDAP objects. Functional attributes are used for managing directories. Functional attributes are added to each schema class of the parent function.
  
  NOTE: To map the operational attributes in One Identity Manager, custom extensions to the One Identity Manager schema may be required. Use the Schema Extension program to do this.
- Auxillary class assigment: Use schema function to assign additional auxiliary classes to structural classes. Auxiliary classes are classes of Auxiliary type and contain attributes for extending structural classes. Auxiliary class attributes are offered as optional attributes for structural classes in the schema.
  
  NOTE: To map the attributes of the auxiliary classes in One Identity Manager, custom extensions to the One Identity Manager schema may be necessary under certain circumstances. Use the Schema Extension program to do this.
- Switch type of object classes: Use this schema function to change the type of an object class. This may be necessary if a non-RFC compliant LDAP system allows assignment of several structural object classes to one entry although only one structural class is allowed.
  
  Assigning more than one structural class means that an LDAP entry cannot be uniquely assigned to a schema type. If structural object classes have been defined that only serve as property extensions (meaning auxiliary classes), you can, with help from this option, set the connector to handle the object class as an auxiliary class.
  
  NOTE: Object classes that are configured as auxiliary are subsequently not handled as independent schema types and cannot, therefore, be synchronized separately.
- Cache Schema: This schema function keeps the LDAP schema stored in local cache. It is recommended to queue this function after the schema has loaded. This accelerates synchronization and provisioning of LDAP objects.
  
  The cache is stored on the computer used to create the connection, under %Appdata%\...\Local\One Identity\One Identity Manager\Cache\LdapConnector.
- Load AD LDS schema extension: This schema function loads additional information required for synchronizing the Active Directory Lightweight Directory Service.
Adding, editing, or deleting schema functions
To add a schema function
1. In the LDAP schema extensions pane, click .
2. In the menu, select the schema function and click .
  
  Change the order of the schema functions using and .
To edit a schema function
- In the LDAP schema extensions pane, select the schema function and edit the configuration in the detailed view.
To delete a schema function
- In the LDAP schema extensions pane, select the schema function and click .
On the Search base page, define the root entry (normally the domain) that serves as the basis of the search queries. In the Search base menu, select an entry or enter a root value.
You can save the connection data on the last page of the system connection wizard.
- Set the Save connection locally option to save the connection data. This can be reused when you set up other synchronization projects.
- Click Finish, to end the system connection wizard and return to the project wizard.

On the One Identity Manager Connection tab, test the data for connecting to the One Identity Manager database. The data is loaded from the connected database. Reenter the password.
NOTE:
- If you use an unencrypted One Identity Manager database and have not yet saved any synchronization projects to the database, you need to enter all connection data again.
- This page is not shown if a synchronization project already exists.
The wizard loads the target system schema. This may take a few minutes depending on the type of target system access and the size of the target system.

On the Restrict target system access page, specify how system access should work. You have the following options: Read-only access to target system.

Table 5: Specify target system access
Option	Meaning
	Specifies that a synchronization workflow is only to be set up for the initial loading of the target system into the One Identity Manager database. The synchronization workflow has the following characteristics: Synchronization is in the direction of One Identity Manager. Processing methods in the synchronization steps are only defined for synchronization in the direction of One Identity Manager.
Read/write access to target system. Provisioning available.	Specifies whether a provisioning workflow is set up in addition to the synchronization workflow for the initial loading of the target system. The provisioning workflow displays the following characteristics: Synchronization is in the direction of the Target system. Processing methods are only defined in the synchronization steps for synchronization in the direction of the Target system. Synchronization steps are only created for such schema classes whose schema types have write access.

On the Synchronization server page, select the synchronization server to run the synchronization.

If the synchronization server is not declared as a Job server for this target system in the One Identity Manager database yet, you can add a new Job server.
1. Click to add a new Job server.
2. Enter a name for the Job server and the full server name conforming to DNS syntax.
  TIP: You can also implement an existing Job server as the synchronization server for this target system.
  - To select a Job server, click .
  This automatically assigns the server function matching this Job server.
3. Click OK.
  The synchronization server is declared as Job server for the target system in the One Identity Manager database.
4. NOTE: After you save the synchronization project, ensure that this server is set up as a synchronization server.

To close the project wizard, click Finish.

This creates and allocates a default schedule for regular synchronization. Enable the schedule for regular synchronization.

This sets up, saves and immediately activates the synchronization project.
NOTE:
- If enabled, a consistency check is carried out. If errors occur, a message appears. You can decide whether the synchronization project can remain activated or not.
  
  Check the errors before you use the synchronization project. To do this, in the General view on the Synchronization Editor‘s start page, click Verify project.
- If you do not want the synchronization project to be activated immediately, disable the Activate and save the new synchronization project automatically option. In this case, save the synchronization project manually before closing the Synchronization Editor.
- The connection data for the target system is saved in a variable set and can be modified in the Synchronization Editor in the Configuration > Variables category.

Identity Manager 9.2.1 - Administration Guide for Connecting to LDAP

Installing One Identity Manager Service with an LDAP connector

Creating a synchronization project for initial synchronization of an LDAP domain

Related topics

Information required to set up a synchronization project

Creating an initial synchronization project for an LDAP domain with the LDAP connector V2

Related topics

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Identity Manager 9.2.1 - Administration Guide for Connecting to LDAP

Installing One Identity Manager Service with an LDAP connector

Creating a synchronization project for initial synchronization of an LDAP domain

Related topics

Information required to set up a synchronization project

Creating an initial synchronization project for an LDAP domain with the LDAP connector V2

Related topics