Subject Directory Attributes Extension Default
447
Parameter
Description
• Select
OtherName
for names with any other
format. This supports
PrintableString
,
IA5String
,
UTF8String
,
BMPString
,
Any
,
and
KerberosName
.
PrintableString
,
IA5String
,
UTF8String
,
BMPString
,
and
Any
are a string which specifies the
path to a base-64 encoded file which sets
the subtree, such as
/var/lib/pki-ca/
othername.txt
.
KerberosName
has the
format
Realm|NameType|NameStrings
, such
as
realm1|0|userID1,userID2
.
OtherName
must have the format
(type)oid,string
. For example,
(IA5String)1.2.3.4,MyExample
.
Source
Specifies an identification source or protocol
to use to generate an ID. The only supported
source is UUID4, which generates a random
number to create the UUID.
Number of Components (NumGNs)
Specifies the number of name components that
must be included in the subject alternative name.
Table B.16. Subject Alternative Name Extension Default Configuration Parameters
B.1.18. Subject Directory Attributes Extension Default
This default attaches a Subject Directory Attributes extension to the certificate. The Subject Directory
Attributes extension conveys any desired directory attribute values for the subject of the certificate.
The following constraints can be defined with this default:
• Extension Constraint; see
Section B.2.3, “Extension Constraint”
.
• No Constraints; see
Section B.2.6, “No Constraint”
.
Parameter
Description
Critical
Select
true
to mark this extension critical; select
false
to mark the extension noncritical.
Name
The attribute name; this can be any LDAP
directory attribute, such as
cn
or
.
Pattern
Specifies the request attribute value to include in
the extension. The attribute value must conform
to the allowed values of the attribute. If the server
finds the attribute, it sets the attribute value in the
extension and adds the extension to certificates.
If multiple attributes are specified and none
of the attributes are present in the request,
the server does not add the Subject Directory
Attributes extension to certificates. For example,
$request.requester_email$
.
Summary of Contents for CERTIFICATE SYSTEM 8.0 - ADMINISTRATION
Page 42: ...20 ...
Page 43: ...Part I Setting up Certificate Services ...
Page 44: ......
Page 190: ...168 ...
Page 208: ...186 ...
Page 223: ...Part II Additional Configuration to Manage CA Services ...
Page 224: ......
Page 256: ...234 ...
Page 270: ...248 ...
Page 280: ...258 ...
Page 292: ...270 ...
Page 293: ...Part III Managing the Subsystem Instances ...
Page 294: ......
Page 408: ...386 ...
Page 438: ...416 ...
Page 439: ...Part IV References ...
Page 440: ......
Page 503: ...Netscape Defined Certificate Extensions Reference 481 OID 2 16 840 1 113730 13 ...
Page 504: ...482 ...
Page 556: ...534 ...
Page 564: ...542 ...