Red Hat CERTIFICATE SYSTEM 8.0 - ADMINISTRATION, Руководство администратора

Страница: 326 / 564

Chapter 13. Basic Subsystem Management
304
</div>
<div id="account">
<dl><dt></dt><dd></dd></dl>
</div>
</div>
Example 13.1. Default RA Header File
The profile
*.vm
files, as with CA profiles, uses a mix of HTML and JavaScript to create the interior
form or index to use in the center of the page, as shown with
index.vm
in
/var/lib/pki-ra/
docroot/ee
in
Figure 13.3, “RA End-Entities Services Page”
. In
Example 13.2, “Excerpt from the
Default User Enrollment Form”
, the HTML in
user.vm
creates the user enrollment form, located in the
/var/lib/pki-ra/docroot/ee/user
directory.
<center>
<table border="0" cellspacing="1" cellpadding="1">
<tr>
<td>UID:</td>
<td><input type=text name=uid value=""></td>
</tr>
<tr>
<td>Full Name:</td>
<td><input type=text name=cn value=""></td>
</tr>
<tr>
<td>Site ID:</td>
<td><input type=text name=site_id value=""></td>
</tr>
<tr>
<td>Your Email:</td>
<td><input type=text name=email value=""></td>
</tr>
</table>
</center>
Example 13.2. Excerpt from the Default User Enrollment Form
13.3.3. Setting Limits on Searches through the CA End-Entities
Pages
Large PKIs can have tens of thousands, even millions, of certificates, keys, and requests maintained
in its databases. When users search for their certificates or agents list requests, then, it is possible
for thousands or millions of entries to be returned. Large search results can significantly affect CA
performance, so it is possible to limit the number of results returned for a search or the amount of time
that searches can take.
There are two files that can manage search limits for the CA end-entities pages:
• The
CS.cfg
file in the
/var/lib/pki-ca/conf
directory
• The
web.xml
file in the
/var/lib/pki-ca/webapps/ca/WEB-INF
directory
The
CS.cfg
file has a single parameter which can set the maximum number of returned results for all
user interfaces for all search types. To set this value:
1. Stop the CA instance. For example: