Naming and Directory Services (DNS, NIS, and LDAP)

LDAP Client ProfilesTo simplify Solaris client setup, and avoid having to reenter the same information foreach and every client, create a single client profile on the directory server. This way, asingle profile defines the configuration for all clients configured to use it. Anysubsequent change to the profile attributes is propagated to the clients at a ratedefined by the refresh interval.These client profiles should be stored in a well-known location on the LDAP server.The root DN for the given domain must have an object class of nisDomainObjectand a nisDomain attribute containing the client’s domain. All profiles are located inthe ou=profile container relative to this container. These profiles should be readableanonymously.Client Profile AttributesThe following table shows the Solaris LDAP client’s profile attributes, which can be setautomatically when you run idsconfig. See “Initializing a Client Manually”on page 181 and the idsconfig(1M) man page for information on how to set a clientprofile manually.TABLE 9–2 Client Profile AttributesAttributecnpreferredServerListDescriptionThe profile name. The attribute has no defaultvalue. The value must be specified.The host addresses of the preferred servers is aspace separated list of server addresses. (Do notuse host names.) The servers in this list are triedin order before those in defaultServerListuntil a successful connection is made. This hasno default value. At least one server must bespecified in either preferredServerList ordefaultServerList.Chapter 9 • LDAP Basic Components and Concepts (Overview) 137