Neoview User Management and Security Administration Guide (R2.5)

NOTE: Entries you make in the HPDM Common Parameters box overwrite any corresponding
values in the default configuration entry. For example, if you define three servers of the
openLDAP type and make some changes in the Common Parameters when you define the third
server, those values will be used by default for any additional servers you define and will also
retroactively affect the configurations already defined. If you use Active Directory, you can edit the
Common Parameters only when you add or edit the configuration of a Global Catalog server;
HPDM does not allow you to edit Common Parameters when you add or edit the configuration
of a Domain Controller.
Configuration Description File for Use with NCI
The configuration description file is a text file that assigns values to various LDAP server
configuration parameters. Because different servers can have different configuration requirements,
you can create a different configuration description file for each server or reuse the same file for
any servers that have exactly the same parameters.
In addition to the files you create for individual servers, you should also create a default
configuration description file. The default configuration description file includes parameters that
must have the same value across all LDAP servers. It can also include parameters that vary across
servers but occur in enough cases to be used by default; for example, although the
UniqueIdentifier might vary from server to server, the default configuration can specify the
value to be used if you omit the parameter when adding a particular server. For more information
about defining the default configuration, see “Attributes of Directory Server Configurations”
(page 78).
Each line that assigns a value to a configuration parameter has the following format:
parameter value
as in
DirectoryBase o=REScorp.com
Also permissible in the configuration description file are blank lines and comment lines. A blank
line, a line containing just spaces, or a line in which the first character is a hash sign (#) is treated
as a comment. All such lines are retained when the contents of the file are stored internally, so
if you use an INFO SERVER command to display the configuration, you will see the text in its
original format.
Any line that is not blank and does not start with a hash sign is presumed to assign a value to a
configuration parameter. All text between the final space or tab and the end of the line is
interpreted as the value you are assigning to the parameter. A parameter value can contain any
ASCII character in the range 32 to 126.
The infrastructure reports an error if
• A line begins with a term that doesn't correspond to a supported parameter
• An expected parameter is omitted, and there is no default
• The configuration file defines multiple instances of a parameter that should be defined only
once per LDAP server configuration
The next few pages describe the parameters you can include in the configuration description
file. With the exception of UniqueIdentifier, each parameter can occur only once in the
configuration description file. In addition, certain parameters are valid only in the default
configuration file, as indicated in the column labeled “Restrictions”; this practice ensures that
those values are uniform across all LDAP servers. Other parameters can have different values
for different LDAP servers. It is a good practice to define the default configuration first, then
create configuration description files for specific LDAP servers.
68 LDAP Server Configuration on Neoview