LDAP-UX Client Services B.04.00 Administrator's Guide

Installing And Configuring LDAP-UX Client Services
Plan Your Installation
Chapter 2 15
If you are familiar with NIS, one example is to create a separate
profile for each NIS domain.
Where in your directory will you put your profile?
The profile contains directory access information. It specifies how
and where clients can find user and group data in the directory. You
can put the profile anywhere you want as long as the client systems
can read it. For example, you might put it near your user data, or in a
separate administrative area. You should put the profile in the same
directory as your user and group data to simplify access permissions.
Clients must have access to both the profile and the user and group
data. The following example shows a configuration profile DN of
cn=profile1,ou=profiles,ou=devices,ou=unix,o=hp.com.
Figure 2-1 Example Directory Structure
Write your configuration profile DN on the worksheet in Appendix A,
“Configuration Worksheet,” on page 183.
By what method will client systems bind to the directory?
Clients can bind to the directory anonymously. This is the default
and is simplest to administer. If you need to prevent access to your
data from anonymous users or your directory does not support
anonymous access, you can use a proxy user. If you configure a proxy
user, you can also configure anonymous access to be attempted in the
event the proxy user fails.
Write your client access method and proxy user DN, if needed, on the
worksheet in Appendix A, “Configuration Worksheet,” on page 183.
o=hp.com
ou=unix
ou=people ou=groups ou=profiles
user
data
profile1group
data
ou=hosts
host
data