Appendix A, .conf Parameters 85
location-suffix
Description 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.
Format location-suffix “<suffix>”
Example location-suffix “o=airius.com”
newtype
Description Defines the types of entries that can be added to the directory using the
gateway. The newtype parameter 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.
Format 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:
• orgperson—corresponds to the display-orgperson.html template. Defines
how the gateway displays an entry of object class type inetOrgPerson.
• groupun—corresponds to the display-groupun.html template. Defines how
the gateway displays an entry of object class type groupOfUniqueNames.
• orgunit—corresponds to the display-orgunit.html template. Defines how the
gateway displays an entry of object class type organizationalUnit.
• org—corresponds to the display-org.html template. Defines how the
gateway displays an entry of object class type organization.
<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.
