Authoritykeyidentifierext - Red Hat CERTIFICATE SYSTEM 7.1 - ADMINISTRATOR Administrator's Manual

Extension-Specific Policy Module Reference
Table 12-15 AuthInfoAccessExt Configuration Parameters (Continued)
Parameter Description
•
•
•
•

AuthorityKeyIdentifierExt

The
AuthorityKeyIdentifierExt
Identifier Extension to certificates. The extension is used to identify the public key that
corresponds to the private key used by a CA to sign certificates.
For general information about this extension, see "authorityKeyIdentifier" on page 731.
For information on setting the subject key identifier extension in certificates, see
"SubjectKeyIdentifierExt" on page 540.
During installation, CS automatically creates an instance of the authority key identifier
extension policy, named
492 Red Hat Certificate System Administrator's Guide • September 2005
If you selected URL, the value must be a non-relative universal resource identifier (URI)
following the URL syntax and encoding rules. That is, the name must include both a
scheme (for example, http) and a fully qualified domain name or IP address of the host.
For example, http://ocspResponder.example.com:8000
If you selected iPAddress, the value must be a valid IP address specified in
dot-separated numeric component notation. The syntax for specifying the IP address is as
follows:
IPv4 address must be in the n.n.n.n format; for example, 128.21.39.40. IPv4
address with netmask must be in the n.n.n.n,m.m.m.m format. For example,
128.21.39.40,255.255.255.00.
For IP version 6 (IPv6), the address should be in the form with netmask separated by a
comma. Examples of IPv6 addresses with no netmask are 0:0:0:0:0:0:13.1.68.3
and FF01::43. Examples of IPv6 addresses with netmask are
0:0:0:0:0:0:13.1.68.3,FFFF:FFFF:FFFF:FFFF:FFFF:
FFFF:255.255.255.0 and
FF01::43,FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FF00:0000.
If you selected OID, the value must be a unique, valid OID specified in dot-separated
numeric component notation. Although you can invent your own OIDs for the purposes of
evaluating and testing this server, in a production environment, you should comply with
the ISO rules for defining OIDs and for registering subtrees of IDs. See <<<XREF
Appendix B, "Object Identifiers">>>
example, 1.2.3.4.55.6.5.99.
If you selected otherName, the value must be the absolute path to the file containing the
base-64 encoded string of the location. For example,
/usr/netscape/servers/ext/aia/othername.txt.
AuthorityKeyIdentifierExt
for information on allocating private OIDs. For
plug-in module enables you to add the Authority Key
, that is enabled by default.