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

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

Customizing Web Services Pages
301
pkiconsole https://server.example.com: admin_port/subsystem_type
The
subsystem_type
can be
ca
,
kra
,
ocsp
, or
tks
. For example, this opens the DRM console:
pkiconsole https://server.example.com:10445/kra
If DNS is properly configured, then an IPv4 or IPv6 address can be used to connect to the console.
For example:
pkiconsole https://1.2.3.4:9445/ca
pkiconsole https://[00:00:00:00:123:456:789:00:]:9445/ca
13.3. Customizing Web Services Pages
All of the subsystems have some kind of web-based services page for agents and some for other
user types, like administrators or end entities. These web-based services pages use basic HTML and
JavaScript, which can be customized to use different colors, logos, and other design elements to fit in
with an existing site or intranet.
The CA, DRM, OCSP, and TKS have web directories in /var/lib/
subsystem_name
/
webapps/
subsystem_name
, with sub-directories for admin, agent, and end-entities services. The
RA and TPS, which use Apache as their web server instead of Tomcat, have a docroot directory,
/
var/lib/ subsystem_name /docroot
, which contains sub-directories for their different interfaces,
meaning admin, agent, and end-entities for the RA and the different Enterprise Security Client web UIs
and admin pages for the TPS.
While any of the web services pages can be customized, the CA and RA end-entities pages are the
most likely to be edited because they are public-facing.
TIP
For tutorials on HTML editing, see
http://htmlprimer.com/
.
Section 13.3.1, “Customizing CA End-Entities Pages”
and
Section 13.3.2, “Customizing RA End-
Entities Pages”
are not exhaustive examples of the web pages available to edit for all subsystems or
all web service interfaces. These are examples of common files and interfaces to customize.
13.3.1. Customizing CA End-Entities Pages
All of the files for the end-entities services page is in
/var/lib/pki-ca/webapps/ca/ee/ca
.
As shown in
Figure 13.2, “CA End-Entities Services Page”
, the CA end-entities page is comprised of
two files. The
index.html
file defines the header and the left menu. The center area is made up of
different template files for most pages and HTML files for the profile enrollment forms.