To use a directory service, you must:
Configure the LDAP server according to the vendor-supplied documentation.
Add the location of the LDAP libraries to the Unix load library path environment variable for your platform.
Configure the libtcl.cfg file to use directory services.
Use any standard ASCII text editor to:
Remove the semicolon (;) comment markers from the beginning of the LDAP URL lines in the libtcl.cfg file under the [DIRECTORY] entry.
Add the LDAP URL under the [DIRECTORY] entry. See Table 6-3 for supported LDAP URL values.
WARNING! The LDAP URL must be on a single line.
libtcl.cfg ldap+libsydblad.so ldap://host:port/ditbase??scope??bindname=username password libtcl64.cfg ldap=libsydbldap64.so ldap://host:port/ditbase??scope??bindname=username password
For example:
[DIRECTORY] ldap=libsydbldap.so ldap:///huey:11389/dc=sybase,dc=com??one?? bindname=cn=Manager,dc=sybase,dc=com secret
“one” indicates the scope of a search that retrieves entries one level below the DIT base.
Table 6-3 defines the keywords for the ldapurl variables.
Keyword |
Description |
Default |
|---|---|---|
host (required) |
The host name or IP address of the machine running the LDAP server |
None |
port |
The port number that the LDAP server is listening on |
389 |
ditbase (required) |
The default DIT base |
None |
username |
Distinguished name (DN) of the user to authenticate |
NULL (anonymous authentication) |
password |
Password of the user to be authenticated |
NULL (anonymous authentication) |
Verify that the appropriate environment variable points to the required third-party libraries. The Netscape LDAP SDK libraries are located in $SYBASE/$SYBASE_OCS/lib3p or lib3p64.The Unix load library path environment variable must point to this directory.
Add your server entry to the LDAP server using dscp or dsedit. See “Adding a server to the directory services”.
