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
| Server function |
LDAP connector |
| Machine role |
Server | Jobserver | 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).
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.
-
Remotely installs One Identity Manager Service components corresponding to the machine roles.
-
Configures the One Identity Manager Service.
-
Starts the One Identity Manager Service.
NOTE: The program performs a remote installation of the One Identity Manager Service. Local installation of the service is not possible with this program.
To remotely install the One Identity Manager Service, you must have an administrative workstation on which the One Identity Manager components are installed. For detailed information about installing a workstation, see the One Identity Manager Installation Guide.
NOTE: 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 detailed information about setting up Job servers, see the One Identity Manager Configuration Guide.
To remotely install and configure One Identity Manager Service on a server
-
Start the Server Installer program on your administrative workstation.
-
On the Database connection page, enter the valid connection credentials for the One Identity Manager database.
-
On the Server properties page, specify the server on which you want to install the One Identity Manager Service.
-
Select a Job server from the Server menu.
- OR -
To create a new Job server, click Add.
-
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 detailed information about configuring the service, see the One Identity Manager Configuration Guide.
-
To configure remote installations, 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.
-
If the database is encrypted, on the Select private key file page, select the file with the private key.
-
On the Service access page, enter the service's installation data.
-
Computer: Enter the name or IP address of the server that the service is installed and started on.
-
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.
Use the Synchronization Editor to configure synchronization between the One Identity Manager database and LDAP environment. The following describes the steps for initial configuration of a synchronization project. For more information about setting up synchronization, see the One Identity Manager Target System Synchronization Reference Guide.
After the initial configuration, you can customize and configure workflows within the synchronization project. Use the workflow wizard in the Synchronization Editor for this. The Synchronization Editor also provides different configuration options for a synchronization project.
Related topics
Have the following information available for setting up a synchronization project.
Table 4: Information required for setting up a synchronization project
|
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.
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.
The remote connection server and the workstation must be in the same Active Directory domain.
Remote connection server configuration:
-
One Identity Manager Service is started
-
RemoteConnectPlugin is installed
-
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 as remote connection server at the same time, by simply installing the RemoteConnectPlugin as well.
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:
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 the LDAP connector.
-
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.
Enable the Connect using remote connection server option and select the server to be used for the connection under Job server.
-
Specify settings for the wizard using Configure advanced settings (expert mode) on the wizard's start page.
-
If you use a default project template, disable this option. The default templates automatically find which settings to use.
-
For customized LDAP systems, enable the option. You can set the following options for this case:
-
Definition of virtual classes for non-RFC compliant object mappings
-
Definition of auxiliary classes of Auxiliary type
-
Definition of system attributes for object identification, revision properties and additional operational attributes
-
Definition of additional attributes for supporting dynamic groups
For more information, see Advanced settings of a generic LDAP connector.
-
On the Network page, enter network settings for the LDAP server connection.
-
In the Host pane, enter the connection settings for the LDAP 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.
-
Click Test.
The system tries to connect to the server.
-
On the Additional settings pane, enter the additional settings for communication with the LDAP server.
-
Protocol version: Version of the LDAP protocol. The default value is 3.
-
No encryption: Specifies that no encryption is used.
-
SSL/TLS encryption: Specifies whether the connection is SSL/TLS encrypted.
-
Use StartTLS: Specifies whether StartTLS is used.
-
Enter authentication data on the Authentication page.
-
In the Authentication method pane, select the authentication type for the login to the target system.
-
Depending on the selected authentication method, additional information may be required. Enter this information under Credentials.
-
User name: Name of the user account for logging in to LDAP.
-
Password: Password for the user account.
-
Enable sealing: Specifies whether sealing is enabled. Set this option if the selected authentication method supports sealing.
-
Enable signing: Specifies whether signing is enabled. Set this option if the selected authentication method supports signing.
-
On the Verify LDAP connection pane, click Test connection.
An attempt is made to log into the server.
-
The LDAP server information page displays the information about the LDAP schema.
-
On the Search options page, specify the search parameters for finding the LDAP objects to be loaded. You can configure the following settings:
-
Cache LDAP schema locally: Specifies whether the LDAP schema should be kept in local cache. 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\GenericLdapConnector.
-
Request timeout (seconds): Timeout for LDAP requests in seconds. (Standard 3600)
-
Use paged search: Specifies whether LDAP objects are loaded by page. If you set this option, you include the page size.
-
Page size: Maximum number of objects to load per page. (Default 500)
-
On the Modification capabilities page, specify the kind of write operations supported by the LDAP server.
-
Enable the Server supports renaming of entries option if the LDAP server supports renaming of entries.
-
Enable the Server supports moving of entries option if the LDAP server supports moving of entries.
NOTE: Some servers only support renaming of entries on leaf nodes. In this case, you will get an error message when trying to rename other nodes.
-
Enable the Use DeleteTree control when deleting entries option if you want the LDAP server to sent the DeleteTree control to delete entries with sub-entries during deletion.
-
Specify additional password settings for user accounts on the Password settings page. Enter the following settings.
-
Password attribute: An attribute that represents the password of a user account, for example, userPassword.
-
Password change method: A method you can use to change passwords. Permitted values are:
-
Default: Default method for changing the passwords. The password is written directly to the password attribute.
-
ADLDS: A password change method used for systems that are based on Microsoft Active Directory Lightweight Directory Services (AD LDS).
-
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.
-
Select a project template on the Select project template page to use for setting up the synchronization configuration. Available project templates are:
-
OpenDJ Synchronization: The project template is based on OpenDJ. Use this project template for initially setting up the synchronization project. For custom implementations, you can extend the synchronization project with the Synchronization Editor.
-
AD LDS Synchronisation: The project template is based on Active Directory Lightweight Directory Services (AD LDS).
- On the Restrict target system access page, specify how system access should work. You have the following options:
Table 5: Specify target system access
Read-only access to target system.
|
|
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:
|
|
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 in the One Identity Manager database yet, you can add a new Job server.
-
Click 
to add a new Job server.
-
Enter a name for the Job server and the full server name conforming to DNS syntax.
- Click OK.
The synchronization server is declared as Job server for the target system in the One Identity Manager database.
-
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.
Related topics
