+

Search Tips   |   Advanced Search

Configure an IBM Security Directory Server source endpoint

To configure an Security Directory Server as a endpoint, you must specify the LDAP URL, login name with credentials, the search base, and root suffix.


Before you begin

Ensure that you create an endpoint and specify the type as IBM Security Directory Server. See Configure endpoints.


Procedure

  1. On the IBM Security Directory Server source endpoint configuration page, in the LDAP URL field, enter the LDAP URL of the IBM Security Directory Server that you want to access.

    The LDAP URL format is ldap://hostname:port or ldap://server_IP_address:port.

    For example: ldap://localhost:389

    Note: The default LDAP port number is 389. If you are using SSL, the default LDAP port number is 636.

  2. In the User Login and Password fields, enter the distinguished name and credentials for authentication to the server.

    For example: cn=root

  3. In the Include entries from the following container field, enter the directory server search base that is polled for changes. Alternately, we can click Contexts and select from the LDAP Search Base list and then click OK.

    For example: o=sample

  4. To verify the IBM Security Directory Server connection settings, click Test Connection. If the connection is successful, the attributes in the endpoint are displayed in a separate pane. We can use the Filter field to search the attributes.
  5. Optional: We can also configure the following advanced parameters. Expand the Advanced section to view these parameters.

      Seconds Before Timeout
      Specify the maximum number of seconds to wait for the next changed directory server object. The default value is 0.
      Seconds Between Polling
      Specifies the number of seconds to sleep between successive polls. The default value is 60.
      Change State Key
      Specifies the name of the key or parameter that stores the change detection iterator state. The state key is used between runs to remember the last changed that was processed. If synchronization was stopped for any reason, when it is restarted, it can pick up from where it stopped.
      The value of this key must be unique for each endpoint. If you do not set this parameter, a value is computed automatically to ensure uniqueness.
      Binary Attributes
      Specify a list of attributes that must be interpreted as binary values instead of strings. When you enter the attribute names in this field, enter one attribute per line and do not use any separators.
      Page Size
      Number of entries per page that must be returned by the request.


What to do next

After configuring the endpoint, we can create a flow to define the relationship between the endpoint and the target directory server.


Parent topic:

Configure endpoints