![]() |
CommuniGate Pro LDAP Module |
|||||||||||||||||||||||||||||||||||||||
|
|
Note: while LDAP and Central Directory services are often considered to be the same, this is not correct, especially for the CommuniGate Pro Server. The LDAP module can provide access to various Server database objects, not only to the Central Directory database. On the other hand, the Central Directory database can be used not only by LDAP clients, but it can also be browsed via the WebUser Interface and it can be used by other Server components and modules.
This section describes the LDAP module (server) only, not the Central Directory database. Please see the Central Directory section for more details.
Note: while the LDAP module implements an LDAP server functionality, the CommuniGate Pro Server can also work as an LDAP client, using the LDAP protocol to access external LDAP servers and their databases. Usually this is implemented using the .ldb database objects.
The CommuniGate Pro LDAP module provides access to the Central Directory data base as well as to any number of supplementary databases.
This is essential to understand that the CommuniGate Pro LDAP module itself dose not provide any Central Directory or other services. It just implements a database access protocol, and the functionality it provides depends on the databases maintained by the Server.
Use a Web browser to configure the LDAP module. Open the Access page in the WebAdmin Settings section.
The LDAP module records in the System Log are marked with the LDAP tag. Please note that the LDAP protocol is a binary protocol, so all low-level data is presented in the hexadecimal form.
Note:The pre-4.7 Netscape ® LDAP clients crash if they communicate with a very fast server returning more than 90 records. If your users have this problem, open the Obscure page in the WebAdmin Settings section, and select the Make LDAP Server Slower option. Ask your users to update to the 4.7 or better version of Netscape browser/mailer product.
Note:The Netscape® LDAP client (version 4.7) does not correctly process the "properties" command - it always tries to connect to the port 389, even if the search was successfully made on a different (for example, secure) port.
The LDAP module allows users to employ all authentication methods supported with the CommuniGate Pro Server.
When an LDAP client requests "all available info" about a specific account in the Central Directory, the LDAP module returns not only the Central Directory database information, but that user "public info" data, too. Users can update their public info data using the WebUser and ACAP access methods. Unlike the fields included in the Central Directory itself, the Public Info fields cannot be used for search operations.