Using LDAP with the OpenAccess SDK Clients : Retrieving Connection Information from LDAP Directories

Retrieving Connection Information from LDAP Directories

When an OpenAccess SDK Client retrieves connection information from an LDAP directory, the connection to the OpenAccess SDK Server takes place as a two-step process as shown in the following figure.

1. The OpenAccess SDK Client connects to the LDAP server and retrieves connection information from an LDAP entry.

2. Using the connection information retrieved from the LDAP entry, the OpenAccess SDK Client connects to the OpenAccess SDK Server.

OpenAccess SDK Client requests connection information from the LDAP server, then connects to the OpenAccess SDK Server using information retrieved from the LDAP server.

To retrieve connection information from an LDAP directory, you configure the following information at the OpenAccess SDK Client:

LDAP Server Host	is the TCP/IP host name of the LDAP server.
LDAP Server Port	is the TCP/IP port that the LDAP server is listening on for incoming connection requests. If unspecified, the OpenAccess SDK Client will use the default LDAP port 389.
Distinguished Name (DN)	is an identifier that uniquely identifies the LDAP entry where connection information is stored. See for information about what you must include in an LDAP entry.

For information about configuring ODBC Clients and ADO Clients to connect to an LDAP server to retrieve connection information:

See Configuring the ODBC Client

See Configuring the ADO Client

For JDBC Clients, JDBC data sources store connection instructions in a JNDI (Java Naming and Distribution Interface) infrastructure, which can support LDAP. See Connecting to a Data Source for more information.