Netscape Certificate Management System 6.01, Manual

Page: 39 / 377

NISAuth Plug-in Module
Chapter 1 Authentication Plug-in Modules 39
dnpattern
Specifies a string representing a subject name pattern to formulate from the
directory attributes and entry DN.
Permissible values: Any valid DN string composed from standard DN
attributes, which must be separated by commas; see “DNs in Certificate
Management System” on page 312.
The syntax is illustrated in the following example:
E=$attr.mail.1, CN=$attr.cn, OU=$dn.ou.2, O=$dn.o, C=US
This sample configuration specifies that the subject name should be
formulated as follows:
•
E
= the first
mail
LDAP attribute value in the user’s entry
•
CN
= the (first)
cn
LDAP attribute value in the user’s entry
•
OU
= the second
ou
value in the user’s entry DN
•
O
= the (first)
o
value in the user’s entry DN
•
C
= the string
US
If this parameter value is empty or not set, the server uses
E=$attr.mail,
CN=$attr.cn, O=$dn.o, C=$dn.c
as the DN pattern.
This default DN pattern works well with Netscape Communicator and other
browsers. For Communicator, if you leave out
E=
in end-user certificates,
S/MIME may not work correctly (assuming lack of other extensions in the
certificate). Also, if
C=
and
O=
are left out, certificate display looks strange in
Communicator (when the Display Certificate button is clicked).
extendedDN
Specifies the suffix that the server should use for extending the default subject
DN when an LDAP directory for retrieving such information is not specified.
The value you specify in this field is used by the sever to suffix the default
subject name in certificates, which is in the form
CN=<FirstName
LastName>,UID=<UserID>
.
Example: If you assign
OU=People,O=Example Corporation,C=US
as
the extended DN, subject names in certificates would be of this form:
CN=<FirstName LastName>,UID=<UserID>,OU=People,
O=Example Corporation,C=US
Table 1-4
Description of parameters defined in the NISAuth module (Continued)
Parameter Description