Table of Contents
Advertisement
Guidelines for Editing the Configuration File
The following are guidelines for editing the configuration file:
•
The format for parameters is as follows:
#comment
[parameter]=value
•
Comment lines begin with the pound
•
A line beginning with white space is considered a continuation of the previous
line.
•
Comment lines, blank lines, unknown parameters, or misspelled parameters
are ignored by the server.
•
Subsystem-specific parameters are distinguished by a prefix identifying the
subsystem as follows:
for the Certificate Manager
ca
for the Registration Manager
ra
for the Data Recovery Manager
kra
for the Online Certificate Status Manager
ocsp
•
The parameter names and their values are strings. The parameter names can be
hierarchically structured with
ca.Policy.rule.RSAKeyRule.maxSize
level (such as
Policy
corresponding to its higher level (
•
The values that need to be localized (such as distinguished names in multibyte
format) should be entered in
•
The values of some parameters are referenced to other parts of the
configuration file. For example, assume that a parameter is defined as
subsystem.id=ca
parameters beginning with
•
The configuration file supports Unix-style file separator, the forward slash (/).
If the backward slash (\) file separator is required, use two backward slashes
(\\) instead of one.
•
Authentication parameters:
(#)
notation with multiple levels—for example,
'.'
in the example) can be requested from the configuration
in the example).
ca
format.
utf8
; when this parameter is processed by the server, all the
will be used.
ca
character and are ignored.
. The entries corresponding to a lower
Chapter 7
Administrative Basics
Configuration Files
261
Advertisement
Table of Contents
