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

Using Service Search Descriptors toModify Client Access to Various ServicesA service search descriptor (SSD) changes the default search request for a givenoperation in LDAP to a search you define. SSDs are particularly useful if, for example,you have been using LDAP with customized container definitions or anotheroperating system and are now transitional to the latest Solaris release. Using SSDs,you can configure Solaris LDAP naming services without having to change yourexisting LDAP database and data.Setting Up SSDs Using idsconfigAssume your predecessor at Example, Inc. had configured LDAP, storing users inou=Users container. You are now upgrading to the latest Solaris release. Bydefinition, Solaris LDAP client assumes that user entries are stored in ou=Peoplecontainer. Thus, when it comes to searching the passwd service, LDAP client willsearch the ou=people level of the DIT and not find the correct values.One laborious solution to the above problem would be to completely overwriteExample, Inc.’s existing DIT and to rewrite all the exiting applications on Example,Inc.’s network so that they are compatible with the new LDAP naming service. Asecond, far preferable solution would be to use an SSD that would tell LDAP client tolook for user info in an ou=Users container instead the default ou=people container.You would define the necessary SSD during the configuration of the Sun Java SystemDirectory Server using idsconfig. The prompt line appears as follows.Do you wish to setup Service Search Descriptors (y/n/h? yA Add a Service Search DescriptorD Delete a SSDM Modify a SSDP Display all SSD’sH HelpX Clear all SSD’sQ Exit menuEnter menu choice: [Quit] aEnter the service id: passwdEnter the base: service ou=user,dc=west,dc=example,dc=comEnter the scope: one[default]A Add a Service Search DescriptorD Delete a SSDM Modify a SSDP Display all SSD’sH HelpChapter 11 • Setting Up Sun Java System Directory Server With LDAP Clients (Tasks) 165