|Previous Contents Index DocHome Next|
|iPlanet Directory Server Gateway Customization Guide|
Appendix A .conf Parameters
The dsgw.conf and pb.conf files are installed during directory server installation. Associated directives are described in Appendix B, "Gateway Directives."
Specifies the amount of time in seconds before a user's authentication expires in the gateway. When authenticating to the Directory from the gateway, the gateway retains authentication credentials for the amount of time specified in this parameter. Once authentication credentials have expired, the gateway prompts the user to re-authenticate.
For information on authenticating to the directory server using the gateway, see the on-line documentation that is available through the gateway.
The following example causes user authentication to expire in two hours. This is the default expiration time:
Specifies the hostname and port number used to contact the directory server. This parameter also determines the search base used for searches performed from the gateway, and whether the gateway uses SSL to communicate with the directory server.
baseurl [ldap | ldaps]://host:port/search base
ldap | ldaps . Use ldap to have the gateway communicate the directory server without using SSL. Use ldaps to have the gateway communicate with the directory server using SSL.
host. Indicates the hostname of the device where the directory server is installed.
port. Indicates the port number used by the directory server. Always specify a port number even when using standard ldap or ldaps port numbers (389 and 636, respectively).
search base. Indicates the distinguished name representing the point in the directory from which all searches are performed. Normally, searchbase is set to the directory's suffix.
Substitute the following hexadecimal values for the equal sign, space, and comma in the search base:
The following example sets the base URL to use SSL communications to a server running on the well-known LDAP security port (636). The base search address is set to o=siroe.com:
Specifies the location of the file where the bind DN and bind password are stored. This file should be stored separately of the .conf file for the gateway instance. The binddnfile is used to authenticate to the server for non-anonymous searching.
Used by the gateway to substitute ideographic space for non-breaking space (nbsp) in Asian character sets.
changeHTML nbsp_from nbsp_to charset
changeHTML <space character> <space charac ter> Shift_JIS
Defines the default character set for communication with HTTP clients. The default is UTF-8 (Unicode), which supports all the characters in the iPlanet Directory Server. UTF-8 is the preferred character set, however many browsers don't support the UTF-8 charset, or display it poorly.
Some users may require a different character set than the one specified using this parameter. For these users, the charset parameter setting may be overridden by creating a <LANG>/dsgw/charset.conf file which contains the charset name. However, to receive the correct language, users will have to configure their browsers to send the appropriate accept-language headers.
For compatibility with HTTP clients that can't handle an HTTP response with a charset parameter in the content-type, comment out this parameter in the .conf file. this prevents the gateway from sending an explicit charset to gateway clients. When no charset parameter is defined, the gateway by default transmits ISO-8859-1 (Latin-1).
The charset parameter is ignored by Netscape Communicator 4.0 and Internet Explorer 4.0 and greater clients, which request the UTF-8 charset by default. Forcing these clients to use a non-UTF-8 charset (such as Latin-1) requires the ignoreAcceptCharsetFrom parameter, introduced in release 4.0 of the gateway.
More information: ignoreAccetpCharsetFrom
For more information about charsets, see RFC 1345, which defines the syntax of charset names.
For more information about how the 3.x and 4.0 releases of the gateway choose character sets for HTTP clients, see Unicode and iPlanet Support for UTF-8.
Specifies the location of the configuration directory of the gateway. These include the object class templates, search configuration files, search result templates, and script files used to dynamically generate HTML forms for the user.
The configuration directory for the default gateway (dsgw.conf) is ../config. The configuration directory for Directory Express (pb.conf) is ../pbconfig.
Specifies the distinguished name of the directory manager. This is the DN used to bind to the directory server when users authenticate as the directory manager from the gateway. Use a DN other than the root DN for this purpose. It is intended that the DN specified here has read and write authority for the subtree that the gateway sees.
For information on authenticating as the directory manager from the gateway, see the on-line documentation that is available through the gateway.
dirmgr "cn=Directory Manager, o=siroe.com"
For information on the root DN and on setting permissions for the directory, see the iPlanet Directory Server Administrator's Guide.
Used by the gateway CGI scripts to specify the URL to output for HTTP redirection. This needs to be specified as "/dsgw/<htmldir>" and should be the same as the NameTrans set in the HTTP server, if any is being used.
Specifies the location of the HTML files for the gateway. These include the HTML files controlling the appearance of gateway forms.
The HTML directory for the default gateway (dsgw.conf) is ../html. The HTML directory for Directory Express (pb.conf) is ../pbhtml.
Ignores request headers for the UTF-8 character set automatically sent by Netscape Communicator 4.x and Internet Explorer 4.x browsers. Can be used together with the charset parameter to transmit a charset other than Unicode to all gateway clients.
ignoreAcceptCharsetFrom HTTP_ client_version_string
ignoreAcceptCharsetFrom Mozilla/4.01x-NSCP Mozilla/3
More information: charset.
Specifies the location of another config file that should be read by the gateway.
Defines the location choices selectable from the gateway when adding new entries. Each location parameter represents a branch point in the directory tree below which new entries can be added.
location handle "friendly_name""dn"
handle. An arbitrary string used by the location-suffix parameter to map a type of entry to the locations where the entry can be created. For more information, see location-suffix.
friendly_name. An arbitrary string that represents the location. This string should describe the location because the gateway displays this string to users to represent the location.
dn.The distinguished name representing this branch point in the directory. If this value is not terminated with a pound sign, the value specified on the include parameter is appended to this value to build the fully qualified distinguished name. If dn is terminated with a pound sign (#), the value represented here is assumed to be a fully qualified distinguished name, and the pound sign is stripped from the distinguished name before the DN is used by the gateway.
For more information, see include.
The following example defines an entry creation location in a user directory. This location corresponds to the Marketing organizational unit, and the remainder of the distinguished name is built from the value set in the include parameter:
location marketing "Marketing Organization" "ou=Marketing"
A slightly different example defines the same location, but specifies the fully qualified distinguished name:
location marketing "Marketing Organization" "ou=Marketing, o=siroe.com#"
For a more complete example of the location parameter, see Mapping Locations and Entry Types.
Identifies the directory suffix used to create new entries in the directory.
This value is appended to the DN field of the NLS parameter when the gateway is used to create new entries in the directory.
Defines the types of entries that can be added to the directory using the gateway. newtype also defines the locations in the directory where an entry type can be added. For a user to create the entry, the corresponding location must be defined using the location parameter.
newtype template_name "friendly_name" rdnattr locations
template_name. The name of a display-template_name.html file that defines the object class listed. Template files are stored in the ../config directory. The gateway uses these files to define how various types of entries are displayed when entries are being created or viewed:
orgpersoncorresponds to the display-orgperson.html template. Defines how the gateway displays an entry of object class type inetOrgPerson.friendly_name. An arbitrary string that describes the entry. This string should be reasonably descriptive of the entry type because the gateway displays this string to users who are adding entries.
rdnattr. The attribute used to name entries of this type. For example, the default value for the rdnattr field for people entries is uid. This means that any people entries created using the gateway will have DNs of the following format:
The rdnattr field can be modified so that entries are named using a different attribute. For example, to change the rdnattr of the newtype orgperson line from uid to cn, people entries created using the gateway will have cn-based DNs rather than the UID-based DNs (the default setting).
locations. A space-separated list of the locations where this type of entry can be added. The locations in this list must be identical to the handle specified on the corresponding location parameter.
The following example allows persons to be added to the Marketing subtree using the template for organizationalPerson:
newtype orgperson "Person" cn marketing
For a more complete example of the newtype parameter, see Mapping Locations and Entry Types.
Identifies the libNLS data directory, which should contain a directory named "locales", containing the configuration files LANG.ctx, LANG.col, and LANG.txt for each supported language (locale).
Identifies the location of the certificate database used by the gateway when using SSL to communicate with the directory server. The certificate database contains the Certificate Authority issuing the certificate for the directory server.
Maps specific object classes to internal gateway templates. These templates define how a specific object class such as a person, a group, or an organizational unit is displayed in the gateway. The templatename identified has a corresponding HTML template stored in dsgw/conf/.
template template_name object_class
The following example identifies orgperson as the template defining attributes for person and inetorgperson object classes:
template orgperson person inetorgperson
Directory server gateway allows users to view vCards for person and NT person directory entries. The vCard and LDAP specifications define different labels to access information: vCards use properties and LDAP uses attributes. Therefore, there must be a way to map the vCard property names to the LDAP attribute names so that the directory server can locate the information for the vCard display. The vcard-property parameter accomplishes this vCard property to LDAP attribute mapping.
vcard-property vcardprop syntax ldapattr [ldapattr2...]
vcardprop.The name of a vCard property. vCard properties that are currently mapped to LDAP attributes are:
FNThe Formatted Name property. All vCards must have a FN property. By default, FN is mapped to the cn attribute.syntax. A string that describes the nature of the vCard information. The following syntaxes are supported:
cisused for simple strings, such as a person's name or telephone numberldapattr [ldapattr2...]. The attribute(s) to be mapped to the vCard property. This is useful when mapping a vCard property to a custom attribute.
The following example changes the mapping of the NOTE property from the default description attribute to a custom attribute named hobbies:
vcard-property NOTE mls hobbies
Previous Contents Index DocHome Next
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.
Last Updated March 21, 2001