Apple Network Services Location Manager Network User Manual
Page 7
7
If you add an LDAP neighborhood without including a searchbase in the name, the LDAP
plug-in makes two attempts to get data from the server. First, it tries to access the directory
without specifying a searchbase. ( Version 3 LDAP servers can return data when no searchbase
is provided.) If that fails, the plug-in tries again using a searchbase of
c=us
. For example, if you
add a neighborhood named
ldap.example.com
, the plug-in tries these searches:
m
ldap://ldap.example.com
m
ldap://ldap.example.com/c=us
When you set up an LDAP directory to advertise services to NSL, keep these points in mind:
m
The NSL plug-in searches for service URLs (for example, afp://asip.example.com,
ftp://www.example.com, or http://www.example.com) in both the
labeleduri
and
URL
attributes. For best results, use the
labeleduri
attribute. See RFC 2079
for more information.
m
Directory entries are displayed using distinguished names. When possible, use attributes
and names that are easy for a person to interpret, like
cn=Joe Smith
, rather than less
revealing names like
userID=2159
.
m
You can improve performance and readability by organizing the directory so that service
lists contain fewer than 200 entries. For example, the searchbase
ou=printers, o=school
can be restructured as
service=printers, ou=HumanitiesBldg, o=school
service=printers, ou=ScienceBldg, o=school
service=printers, ou=AdminBldg, o=school
m
You can create a separate branch in a directory specifically for NSL browsing.
Example:
ldap.example.com/ou=nsl,c=us
LDAP in Mac OS X
The NSL Manager cannot perform LDAP searches in the first release of Mac OS X.
Setting Up for NBP Searches
If AppleTalk is active on a host, AppleTalk zones and AppleShare servers on the network are
listed in the neighborhood named AppleTalk.
Setting Up for NetInfo Searches
NetInfo is the native directory service on Mac OS X. However NSL Manager does not support
NetInfo searches in the first release of Mac OS X.