Using LDAP as a directory service

Adaptive Server uses directory services to establish client and RPC connections over the network. This chapter provides information about using LDAP directory services to establish connections.

Lightweight Directory Access Protocol (LDAP) is an industry standard for accessing directory services. Directory services allow components to look up information by a distinguished name (DN) from an LDAP server that stores and manages server, user, and software information that is used throughout the enterprise or over a network.

The LDAP server can be located on a different platform from the one on which Adaptive Server or the clients are running. LDAP defines the communication protocol and the contents of messages exchanged between clients and servers. Messages are operators, such as client requests for read, write and query, and server responses, including data-format information.

The LDAP server stores and retrieves information about:

The LDAP server can be configured with these access restrictions:

User name and password authentication properties establish and end a session connection to an LDAP server.

NoteThe user name and password that are passed to the LDAP server for user authentication purposes are distinct and different from those used to access Adaptive Server.

When an LDAP server is specified in the libtcl.cfg libtcl64.cfg or libtcl64.cfg file (collectively the libtcl*.cfg file), the server information is searched for using the ordered list of directory services from the libtcl*.cfg file. If the information is not found there, it then searches the interfaces file.

For the Cluster Edition, an interfaces file may be set in the quorum file. When the quorum file specifies an interfaces file, the Cluster Edition ignores the directory services specified in libtcl*.cfg files.

If multiple directory services are supported in a server, then the order in which they are searched is specified in libtcl*.cfg. You cannot specify the search order with the dataserver command-line option. See “Multiple directory services”.