Working With Oracle® Solaris 11.2 Directory and Naming Services: LDAP

Exit Print View

Updated: July 2014
 
 

Defining Service Search Descriptors

At Example, Inc., the previous LDAP configuration stored user information in the ou=Users container of the directory tree. In the Oracle Solaris release described by this manual, user entries are assumed to be stored in ou=People container. Thus, if the passwd service is searched and the client searches the ou=People container, the information cannot be obtained.

To avoid the complications of re-creating the company's existing directory information tree and its impact on other operations, you can create service search descriptors (SSDs) instead. These SSDs would direct the LDAP client to look for user information from the ou=Users container instead of the default container.

For information about search descriptors, see Service Search Descriptors and Schema Mapping.

To create SSDs, you also use the idsconfig command. The prompt line that refers to SSDs appears as follows:

Do you wish to setup Service Search Descriptors (y/n/h? y
A  Add a Service Search Descriptor
D  Delete a SSD
M  Modify a SSD
P  Display all SSD's
H  Help
X  Clear all SSD's

Q  Exit menu
Enter menu choice: [Quit] a
Enter the service id: passwd
Enter the base: service ou=user,dc=west,dc=example,dc=com
Enter the scope: one[default]
A  Add a Service Search Descriptor
D  Delete a SSD
M  Modify a SSD
P  Display all SSD's
H  Help
X  Clear all SSD's

Q  Exit menu
Enter menu choice: [Quit] p

Current Service Search Descriptors:
==================================
Passwd:ou=Users,ou=west,ou=example,ou=com?

Hit return to continue.

A  Add a Service Search Descriptor
D  Delete a SSD
M  Modify a SSD
P  Display all SSD's
H  Help
X  Clear all SSD's

Q  Exit menu
Enter menu choice: [Quit] q