Netscape Communications Corporation ("Netscape") and its licensors retain all ownership rights to the software
programs offered by Netscape (referred to herein as "Software") and related documentation. Use of the Software and
related documentation is governed by the license agreement accompanying the Software and applicable copyright
law.
Your right to copy this documentation is limited by copyright law. Making unauthorized copies, adaptations, or
compilation works is prohibited and constitutes a punishable violation of the law. Netscape may revise this
documentation from time to time without notice.
THIS DOCUMENTATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IN NO EVENT SHALL
NETSCAPE BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND
ARISING FROM ANY ERROR IN THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION ANY LOSS OR
INTERRUPTION OF BUSINESS, PROFITS, USE, OR DATA.
ONE, SuiteSpot, and the Netscape N and Ship’s Wheel logos are registered trademarks of Netscape Communications
Corporation in the United States and other countries. Other Netscape logos, product names, and service names are
also trademarks of Netscape Communications Corporation, which may be registered in other countries. Other product
and brand names are trademarks of their respective owners.
The downloading, exporting, or reexporting of Netscape software or any underlying information or technology must
be in full compliance with all United States and other applicable laws and regulations. Any provision of Netscape
software or documentation to the U.S. Government is with restricted rights as described in the license agreement
accompanying Netscape software.
The Team
Writer: Doug Meier
Technical Editor, Gateway: Rob Powers
Technical Editor, Gateway Localization: Noriko Hosoi
Netscape Communications Corporation 501 East Middlefield Road, Mountain View, CA 94043
The descriptions, instructions, and examples in this guide can be used to create
and modify a gateway instance to suit the needs of users in your organization.
Who Needs This Guide
This guide is for anyone who needs to implement a simple gateway instance
with basic directory lookup functionality. It is also for users who wish to
implement a more powerful gateway instance with directory authentication and
administration capability. This guide assumes the reader is familiar with HTML
file syntax and has a rudimentary understanding of how the LDAP directory
stores information.
Preface
What’s In This Guide
• Chapter 1, Gateway Features: Describes features and functionality of the
gateways installed with Directory Server 4.x. HTTP server recommendations
are also provided.
• Chapter 2, Setting Up the Gateway: Identifies the planning decisions and
tasks required to install and initially configure a gateway. Includes
instructions for HTTP server configuration, procedures for setting up a new
gateway instance, procedures for changing configuration settings on
existing gateways, and recommendations for configuring gateway clients.
• Chapter 3, Gateway Localization: Describes Netscape support for UTF-8,
explains how the gateway selects a character set, identifies the tasks
required to set up additional gateway locales, and explains how to set up
gateway locales for translation.
• Chapter 4, Files Controlling Gateway Functionality: Identifies gateway file
components, including search configuration files, object class templates,
script files, and search result templates.
iii
Related Information
• Chapter 5, Entry Types and Object Class Attributes: Provides examples of
entry types (objects) defined in the gateway’s .conf file, provides examples
of locations mapped to entry types, and discusses gateway directives.
• Chapter 6, Search Attributes, Filters, and Results: Provides examples for
modifying search attributes, adding search support for a new object,
modifying default search filters, and customizing search results.
• Chapter 7, Customizing Graphics and Color: Describes how to change the
appearance of default gateway forms.
• Appendix A, .conf Parameters: Describes, in alphabetical order, gateway
configuration parameters defined in dsgw.conf and pb.conf.
• Appendix B, Gateway Directives Reference: Describes directives used in
Gateway HTML object class and search result templates.
• Appendix C, CGI Usage: Provides regular expression-type descriptions of
the ways to invoke the CGIs in script files.
• Appendix D, Gateway User Help: Provides instructions for using the
Directory Server 4.0 gateway interface. The information supplied here is
intended to be repurposed as help topics that can be made available to
gateway users from the Help button on gateway forms.
Related Information
For more information about working with Directory Server, see these
documents:
• Netscape Directory Server Installation Guide, Version 4.0
• Netscape Directory Server Administration Guide, Version 4.0
• Netscape Directory Server Release Notes, Version 4.0
• Managing Servers with Netscape Console, Version 4.0
• Netscape Directory Server Deployment Guide, Version 3.0
• Customizing LDAP Settings for Communicator 4.0x
iv Netscape Directory Server Gateway Customization Guide
Contents
Preface ................................................................................................................ iii
Who Needs This Guide ....................................................................................... iii
What’s In This Guide ........................................................................................... iii
Related Information ..............................................................................................iv
Chapter 1 Gateway Features .......................................................................1
What Is a Gateway? ...............................................................................................1
HTTP Server Requirements for Gateways ............................................................2
Gateways Installed with Directory Server 4.0 ......................................................2
HTML and configuration directories specified in pb.conf ...................................6
Embedding GCONTEXT in a Link ........................................................................6
Specifying PCONTEXT in an HTML Form ............................................................7
Setting up .conf file and directories for new gateway instance ........................22
Changing LDAP port in the baseurl parameter ..................................................23
Specifying the Path for Certificate Database ......................................................26
Specifying SSL Communication ...........................................................................26
Creating a locale for Chinese (zh) translation ....................................................35
Mapping of Locations and Entry Types in dsgw.conf .......................................48
Adding Initials attribute to orgperson object class ............................................51
Deleting mobile phone attribute from orgperson object class .........................52
Adding template for subclass airiusPerson ........................................................53
Search Attributes for Person Entry ......................................................................61
Extending Search Preferences to Include Pager Number ..................................63
Editing dsgwsearchprefs.conf to Extend a Search Preference ..........................64
dsgw-people entry configured to search for dateofBirth values .......................65
Creating a new dsgwsearchprefs.conf entry for OrgRole ..................................65
Creating a new dsgwfilter.conf entry for orgrole ...............................................66
Search Filter for Email Address Searches ...........................................................67
Modifying a search filter pattern .........................................................................67
Adding OrgUnit to Search Results for People ....................................................69
Changing color settings using COLOR directives ..............................................76
xvii
xviii Writer’s Guide
Chapter
1
Chapter 1Gateway Features
This chapter describes the gateway features introduced with release 4.0 of the
Directory Server. Topics include:
• What Is a Gateway?
• HTTP Server Requirements for Gateways
• Gateways Installed with Directory Server 4.0
• Non-Anonymous Searching
• Compatibility with Existing Gateways
• Automatic Updates to Directory Configuration
What Is a Gateway?
A gateway is an HTTP-to-LDAP client that lives on an HTTP server. Using
special directives embedded in HTML files, a gateway allows users to access
user directory data using any kind of web browser.
A gateway can be used to perform directory lookup, or to authenticate to the
directory and complete a database administration task, without logging in to
Netscape Console.
Chapter 1, Gateway Features 1
HTTP Server Requirements for Gateways
In Version 4.0 of Netscape Directory Server, many gateway instances can be
defined on one HTTP server, providing access to any number of Directory
Servers. A gateway instance consists of:
• a .conf file, stored in <NSHOME>/dsgw/context, defining the context for a
gateway instance (for instance, dsgw.conf defines the dsgw gateway
instance).
• an HTML directory for object class templates and other files containing
gateway directives used to communicate with the LDAP server.
• a configuration directory for directory search, directory authentication,
language files, and gateway scripts.
HTTP Server Requirements for Gateways
A gateway instance requires an HTTP server capable of communicating with
the LDAP Directory Server.
For optimum performance and highest security, the gateway should be
configured to run under a high-performance HTTP server, such as the Netscape
Enterprise server.
See Also
“HTTP Server Configuration” on page 17
Gateways Installed with Directory Server 4.0
Two gateway instances are installed during Directory Server installation: the
default gateway and Directory Express. The default gateway provides search,
authentication, and entry modification capability. Directory Express is a
customized version designed specifically for use as a corporate phonebook.
The two gateway instances provided with Directory Server are configured to
use the suffix set when the Directory Server was configured, and non-SSL
(Secure Socket Layer) communications. Either can serve as a framework for a
building a more sophisticated gateway instance.
2 Netscape Directory Server Gateway Customization Guide
Gateways Installed with Directory Server 4.0
See Also
“Location of Gateway Files” on page 12
Default Gateway (dsgw.conf)
In addition to the standard search form, the default Gateway provides an
advanced search form, a Directory Server authentication form, and a form for
adding and modifying entries.
The configuration file for the default gateway is at <NSHOME>/dsgw/context/
dsgw.conf.
During Netscape Directory Server 4.0 installation, the default gateway is
configured to use as its HTTP server the Netscape Administration server
installed with the directory. Following Directory Server installation, the default
gateway can be accessed from http://adminhost:adminport/ or directly using
this URL:
Directory Express is designed for use out of the box as a corporate phonebook.
The configuration file for Directory Express is <NSHOME>/dsgw/context/
pb.conf.
Chapter 1, Gateway Features 3
Gateways Installed with Directory Server 4.0
During Netscape Directory Server 4.0 installation, Directory Express is
configured to use as its HTTP server the Netscape Administration server
installed with the directory.
Following Directory Server installation, Directory Express can be accessed from
http://adminhost:adminport/ or directly using this URL:
Release 4.0 of the Directory Server supports multiple gateway instances. Many
gateways can access directory data from the same HTTP server without conflict.
Chapter 1, Gateway Features 5
Support for Multiple Gateway Instances
The .conf files defining the configuration of gateway instances are stored in
<NSHOME>/dsgw/context. Within the .conf file are two parameters specifying
the path names for the HTML and template files for the gateway (see
Example 1.1).
Example 1.1 HTML and configuration directories specified in pb.conf
htmldir../pbhtml
configdir ../pbconfig
Specifying Gateway Configuration to
Gateway CGIs
Information about which .conf file to use is communicated in the QUERY
STRING using a GET, and through a hidden variable on a POST.
GET Operations (GCONTEXT)
In a GET operation, gateway CGIs get the gateway context from the QUERY
STRING in the URL.
Use the GCONTEXT directive in all URLS to gateway CGIs. Embed <!-GCONTEXT --> after the CGI name, as shown in Example 1.2. This directive
will be replaced by the current CGI’s gateway context. The GCONTEXT
directive is the only gateway directive that does not have to be at the beginning
of the line.
In release 3.x, CGIs passed their arguments using PATH_INFO. In 4.0,
PATH_INFO is replaced by the QUERY_STRING, which works better with the
Japanese version of Windows NT, and is functionally equivalent.
6 Netscape Directory Server Gateway Customization Guide
Support for Multiple Gateway Instances
POST Operations (PCONTEXT)
In a POST operation, the CGI posts to the gateway instance specified by a
hidden variable on an HTML form. Each POST operation to a gateway CGI in
an HTML form must use the PCONTEXT directive so that CGIs can pass the
gateway instance to the next page and maintain the state.
For CGI invocations using a POST, put <!-- PCONTEXT --> at the beginning of a
line, as shown in Example 1.3.
The default gateway and Directory Express are available from the page for the
Netscape Administration server (http://host:port)
Release 3.x
To get to a 3.x gateway, users enter the following URL:
http://host:port/dshtml
Chapter 1, Gateway Features 7
Gateway Localization
Gateway Localization
The gateway is designed to allow support for clients in multiple locales.
Gateway Locales
Release 4.0 of the Directory gateway is localized for English, Japanese, French,
and German. Language files are stored in <NSHOME>/dsgw/html/<lang> and
<NSHOME>dsgw/config/<lang>, where <lang> is defined in RFC1766 (for
example, language files for Japanese are stored in /usr/netscape/dsgw/html/ja
and /usr/netscsape/dgw/config/ja[true]). The gateway can be configured to
support additional locales.
Support for the character sets necessary to render a particular locale (language)
must be available in the browser’s configuration. Netscape Communicator
provides support for multiple languages and multiple characters sets.
See Also
“Gateway Locales” on page 34
“Configuring Gateway Clients” on page 27
Character Sets
Release 4.0 of the gateway supports Unicode (specifically, the UTF-8 character
set), the character set containing all of the world’s languages. However,
Unicode or any character set specified in the gateway’s .conf file can be
overridden by the HTTP Accept-charset header sent by the gateway client or by
a character set created for a specific language.
See Also
“How the Gateway Selects a Character Set” on page 32
8 Netscape Directory Server Gateway Customization Guide
Non-Anonymous Searching
Release 3.0 of the gateway allows anonymous searching only. This provides
only the most basic permissions for accessing information in the user directory.
The release 4.0 gateway provides the same functionality but in addition
supports non-anonymous searching. A bind DN and bind password, stored in a
file named binddnfile, can be set up for users to authenticate to the Directory
Server. User permissions for directory access can be defined in the Netscape
Console.
If authentication credentials exist for a user on the Directory Server, these
override the bind DN and bind password in the gateway’s binndnfile. When
authentication credentials expire or are invalid, the gateway attempts to
authenticate the user to the directory using the binddnfile. When no binddnfile
is specified, the gateway instance binds anonymously.
binddnfile
Non-Anonymous Searching
The location of the binddnfile containing bind DNs and bind passwords for
individual users and groups of users is specified in the gateway’s .conf file.
See Also
“binddnfile” on page 81
Do Not Server Up binddnfile over HTTP
The binddnfile contains highly sensitive information. Do not store it under
<NSHOME>/dsgw or in any directory that is served up over HTTP (for instance,
/bin/slapd/server is a good place to store the binddnfile).
Chapter 1, Gateway Features 9
Compatibility with Existing Gateways
Compatibility with Existing Gateways
Release 4.0 of the Directory Server is compatible with previous versions of the
gateway, including release 3.x. Although the HTML files and gateway CGIs are
not interchangeable, a 3.x gateway can access a 4.0 Directory Server, and a 4.0
gateway can access a 3.x Directory Server.
It is not necessary to upgrade a 3.x gateway to release 4.0, however a script is
available to complete this task. On UNIX and NT systems, this migration occurs
automatically when a Directory Server is migrated from release 3.x to release
4.0.
The gateway migration script is described in “Migrating 3.x default Gateways to
Release 4.0” on page 14.
Directory server migration is described in the Release Notes for Directory Server
4.0
Automatic Updates to Directory
Configuration
A script that updates gateway instances with changes to Directory Server
configuration, updatedsgw, is included with the Directory Server installation.
This script searches <NSHOME>/dsgw/context for gateway instances that match
the Directory Server host and port.
The updatedsgw script runs automatically for gateways installed on the
Netscape Administration server managing the Directory Server instance. When
the server port or root DN (or other settings, such as directory manager) for a
Directory Server instance is changed, the Netscape Administration server
managing the Directory Server instance runs the updatedsgw script.
See Also
“Updating the Gateway with Changes to Directory Server Configuration” on
page 15
10 Netscape Directory Server Gateway Customization Guide
Chapter
2
Chapter 2Setting Up the Gateway
This chapter describes the planning decisions and tasks required to install and
initially configure a gateway for access by end users. Topics include:
• Gateway Installation Planning
• HTTP Server Configuration
• Creating a New Gateway Instance (4.0 only)
• Gateway .conf File Configuration
• Configuring Gateway Clients
Gateway Installation Planning
When preparing to deploy a gateway in the enterprise, consider the following
planning issues:
• where to store gateway configuration and HTML files
• how to securely store gateway bind DNs and bind passwords
• how to protect root processes on the HTTP server running the gateway
Chapter 2, Setting Up the Gateway 11
Gateway Installation Planning
• whether to migrate existing gateways to release 4.1 gateways or to let them
• how changes to Directory Server configuration and user directory will be
• which type of HTTP server best suits the needs of your enterprise
Location of Gateway Files
Table 2.1 and Table 2.2 show the locations of gateway files for release 4.0 and
release 3.x.
Gateway Release 4.0
Two gateway instances are installed during Directory Server 4.0 installation:
Directory Express and the default gateway. The .conf files (pb.conf and
dsgw.conf) are stored in /dsgw/context. Additional gateways can be created by
customizing Directory Express or the default gateway.
co-exist
updated on the gateway
Table 2.1 Location of gateway files for release 4.0
Unique gateway instances may have unique HTML directories (for example,
..dsgw/mythml) and template directories (/for example, ..dsgw/myconfig).
However, gateways may also be cloned to use identical HTML and template
directories while pointing to different Directory Servers or different suffixes on
a Directory Server.
12 Netscape Directory Server Gateway Customization Guide
Loading...
+ 126 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.