Table of Contents
Advertisement
Overview of Extension-Specific Policy Modules
•
OCSPNoCheckExt Plug-in Module (page 217)
•
PolicyConstraintsExt Plug-in Module (page 221)
•
PolicyMappingsExt Plug-in Module (page 224)
•
PrivateKeyUsagePeriodExt Plug-in Module (page 228)
•
RemoveBasicConstraintsExt Plug-in Module (page 230)
•
SubjectAltNameExt Plug-in Module (page 232)
•
SubjectDirectoryAttributesExt Plug-in Module (page 238)
•
SubjectKeyIdentifierExt Plug-in Module (page 242)
Overview of Extension-Specific Policy Modules
To enable you to add standard and private extensions to end-entity certificates,
Certificate Management System provides a set of policy plug-in modules; each
module enables you to add a particular extension to a certificate request. Plug-in
modules are implemented as Java classes and are registered in the CMS policy
framework. The Policy Plugin Registration tab of the CMS window (Figure 4-1)
lists all the modules that are registered with a CMS instance.
Note that the name of the Java class for a policy plug-in module is in this format:
com.netscape.cms.policy.<plugin_name>
where
for the
com.netscape.cms.policy.AuthorityKeyIdentifierExt
When deciding whether to add any of the X.509 v3 certificate extensions, keep in
mind that not all applications support X.509 v3 extensions. Among the applications
that do support extensions, not all applications will recognize every extension. For
general guidelines on using extensions in certificates, see Appendix C, "Certificate
and CRL Extensions."
128
Netscape Certificate Management System Plug-Ins Guide • May 2002
is the name of a plug-in module. For example, the Java class
<plugin_name>
AuthorityKeyIdentifierExt
module would be:
Advertisement
Table of Contents
