@mukundha@apigee.com See the description below
slapd will by default serve ldap:/// (LDAP over TCP on all
interfaces on default LDAP port). That is, it will bind using
INADDR_ANY and port 389. The -h option may be used to specify
LDAP (and other scheme) URLs to serve. For example, if slapd is
given -h "ldap://127.0.0.1:9009/ ldaps:/// ldapi:///" , It will
bind 127.0.0.1:9009 for LDAP, 0.0.0.0:636 for LDAP over TLS, and
LDAP over IPC (Unix domain sockets). Host 0.0.0.0 represents
INADDR_ANY. A space separated list of URLs is expected. The
URLs should be of the LDAP, LDAPS, or LDAPI schemes, and gener-
ally without a DN or other optional parameters (excepting as
discussed below). Support for the latter two schemes depends on
selected configuration options. Hosts may be specified by name
or IPv4 and IPv6 address formats. Ports, if specified, must be
numeric. The default ldap:// port is 389 and the default
ldaps:// port is 636. The socket permissions for LDAP over IPC
are indicated by "x-mod=-rwxrwxrwx", "x-mod=0777" or "x-
mod=777", where any of the "rwx" can be "-" to suppress the
related permission (note, however, that sockets only honor the
"w" permission), while any of the "7" can be any legal octal
digit, according to chmod(1). While LDAP over IPC requires
write permissions on the socket to allow any operation, the
other listeners can take advantage of the "x-mod" extension to
apply rough limitations to users, e.g. allow read operations
("r", which applies to search and compare), write operations
("w", which applies to add, delete, modify and modrdn), and exe-
cute operations ("x", which means bind is required). "User"
permissions apply to bound users, while "other" apply to anony-
mous users.
I believe it should be ldap://0.0.0.0:10389 in your case or better change it to localhost:10389 to check if thats the actual issue? want to give it a try ?
LinkedIn
Twitter
