
sun.com \| docs.sun.com	How To Buy \| My Sun \| Worldwide Sites

Previous Contents Index Next Next

Chapter 15

Setting Up Sun ONE Directory Server (Tasks)

This chapter describes how to configure Sun ONE Directory Server (formerly iPlanet Directory Server) to support a network of Solaris LDAP naming services clients. The information is specific to the Sun ONE Directory Server.

Note - You must have already performed all the procedures described in Chapter 11 before you can configure Sun ONE Directory Server to work with Solaris LDAP clients.

Note - A directory server (an LDAP server) cannot be its own client.

This chapter covers the following topics.

Configuring Sun ONE Directory Server Using `idsconfig`

Creating a Checklist Based on Your Server Installation

During the server installation process, you will have defined crucial variables, with which you should create a checklist similar to the one below before launching idsconfig. You can use the blank checklist provided in Blank Checklists.

Note - The information included below will serve as the basis for all examples that follow in the LDAP related chapters. The example domain is of an widget company, Example, Inc. with stores nationwide. The examples will deal with the West Coast Division, with the domain west.example.com

Table 15-1 Server Variables Defined

Variable	Definition for Example Network
Port number at which an instance of the directory server is installed (DEFAULT=389)	`default`
Name of server	`myserver` (from the FQDN ipdserver.west.example.com or 192.168.0.0)
Replica server(s) (IPnumber:port number)	`192.168.0.1` [for ipdrep.west.example.com]
Directory manager [`dn: cn=directory manager`]	`default`
Domain name to be served	`west.example.com`
Maximum time (in seconds) to process client requests before timing out	`--1`
Maximum number of entries returned for each search request	`--1`

Note - If you are using hostnames in defining defaultServerList or preferredServerList, you MUST ensure LDAP is not used for hosts lookup. This means ldap must not be in /etc/nsswitch.conf hosts line.

Table 15-2 Client Profile Variables Defined

Variable	Definition for Example Network
Profile name	`WestUserProfile`
Server list (defaults to the local subnet)	west.example.com or `192.168.0.0`
Preferred server list (listed in order of which server to try first, second, and so on)	`none`
Search scope (number of levels down through the directory tree. '`One`', the default, or '`Sub`')	`one` (default)
Credential used to gain access to server. Default is `anonymous`	`proxy`
Follow Referrals? ( a pointer to another server if the main server is unavailable) Default is `no`.	`Y`
Search time limit (default is 30 seconds) for waiting for server to return information.	`default`
Bind time limit (default is 10 seconds) for contacting server. The default is seconds.	`2`
Authentication method Default is `none`.	`simple`

Note - Client profiles are defined per domain. At least one profile must be defined for a given domain.

Attribute Indexes

idsconfig indexes the following list of attributes for improved performance.

`membernisnetgroup`	`pres,eq,sub`
`nisnetgrouptriple`	`pres,eq,sub`
`memberuid`	`pres,eq`
`uidNumber`	`pres,eq`
`gidNumber`	`pres,eq`
`ipHostNumber`	`pres,eq`
`ipNetworkNumber`	`pres,eq`
`ipProtocolNumber`	`pres,eq`
`oncRpcNumber`	`pres,eq`

Schema Definitions

idsconfig(1M) automatically adds the necessary schema definitions. Unless you are very experienced in LDAP administration, do not manually modify the server schema. See Chapter 18, LDAP General Reference (Reference) for an extended list of schemas used by the LDAP naming service.

Using Browsing Indexes

The browsing index functionality of the Sun ONE Directory Server, otherwise known as the virtual list view, provides a way in which a client can view a select group or number of entries from very long list, thus making the search process less time consuming for each client. Browsing indexes provide optimized, predefined search parameters with which the Solaris LDAP naming client can access specific information from the various services more quickly. Keep in mind that if you do not create browsing indexes, the clients may not get all the entries of a given type because the server limits for search time or number of entries might not be enforced.

Indexes are configured on the directory server and the proxy user has read access to these indexes.

Before configuring browsing indexes on the Sun ONE Directory Server, consider the performance cost associated with using these indexes. For more information, refer to the Administration Guide for the version of Sun ONE Directory Server that you are using.

In the following example, note that the -n option denotes the name of the database with the entries to be indexed and the -s option denotes the instance of the directory server.

Note - idsconfig creates all the default VLV indices.
directoryserver -s ipdserver vlvindex -n userRoot -T getgrent directoryserver -s ipdserver vlvindex -n userRoot -T gethostent directoryserver -s ipdserver vlvindex -n userRoot -T getnetent directoryserver -s ipdserver vlvindex -n userRoot -T getpwent directoryserver -s ipdserver vlvindex -n userRoot -T getrpcent directoryserver -s ipdserver vlvindex -n userRoot -T getspent