Understanding LDAP Services for Novell eDirectory
317
no
vd
ocx
(e
n)
6 Ap
ril 20
07
“Enabling Nonstandard Schema Output” on page 323
“Syntax Differences” on page 323
“Supported Novell LDAP Controls and Extensions” on page 324
13.2.1 Connecting to eDirectory from LDAP
All LDAP clients bind (connect) to Novell eDirectory as one of the following types of users:
[Public] User (Anonymous Bind)
Proxy User (Proxy User Anonymous Bind)
NDS or eDirectory User (NDS User Bind)
The type of bind the user authenticates with determines the content that the LDAP client can access.
LDAP clients access a directory by building a request and sending it to the directory. When an
LDAP client sends a request through LDAP Services for eDirectory, eDirectory completes the
request for only those attributes that the LDAP client has the appropriate access rights to.
For example, if the LDAP client requests an attribute value (which requires the Read right) and the
user is granted only the Compare right to that attribute, the request is rejected.
Standard login restrictions and password restrictions still apply. However, any restrictions are
relative to where LDAP is running. Time and address restrictions are honored, but address
restrictions are relative to where the eDirectory login occurred—in this case, the LDAP server.
Connecting As a [Public] User
An anonymous bind is a connection that does not contain a username or password. If an LDAP
client without a name and password binds to LDAP Services for eDirectory and the service is not
configured to use a Proxy User, the user is authenticated to eDirectory as user [Public].
User [Public] is a non-authenticated eDirectory user. By default, user [Public] is assigned the
Browse right to the objects in the eDirectory tree. The default Browse right for user [Public] allows
users to browse eDirectory objects but blocks user access to the majority of object attributes.
The default [Public] rights are typically too limited for most LDAP clients. Although you can
change the [Public] rights, changing them will give these rights to all users. Because of this, we
recommend that you use the Proxy User Anonymous Bind. For more information, see
“Connecting
As a Proxy User” on page 317
.
To give user [Public] access to object attributes, you must make user [Public] a trustee of the
appropriate container or containers and assign the appropriate object and attribute rights.
Connecting As a Proxy User
A proxy user anonymous bind is an anonymous connection linked to an eDirectory username. If an
LDAP client binds to LDAP for eDirectory anonymously, and the protocol is configured to use a
Proxy User, the user is authenticated to eDirectory as the Proxy User. The name is then configured in
both LDAP Services for eDirectory and in eDirectory.
The anonymous bind traditionally occurs over port 389 in LDAP. However, during the installation
you can manually configure different ports.
Summary of Contents for EDIRECTORY 8.8 SP2
Page 4: ...novdocx en 6 April 2007...
Page 116: ...116 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 128: ...128 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 255: ...256 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 406: ...408 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 563: ...566 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 573: ...576 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 601: ...604 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...