Netscape Certificate Management System 6.2, Руководство администратора

Страница: 92 / 874

Certificate Manager Deployment Considerations
92 Netscape Certificate Management System Administrator’s Guide • June 2003
• An Administrative interface that is accessible by default only to members of
the Administrator and Auditor group. You specify the first administrator
when you install the subsystem. Administrators can configure any of the
settings of the server. Most basic functionality and subsystem specific
configuration to the subsystem can be done using the administrative interface.
The administrative interface listens to requests on the SSL Administration Port.
This is the port the CMS administrative interface listens to, and that is accessed
by administrators and auditors using the Java based CMS Console GUI
application.
• An Agent Services interface that is accessible by default only to members of the
Agent group. You can choose to include the first administrator to also be the
first agent when you install the subsystem. Agents are users who can perform
tasks associated with the processing of requests and management of
certificates. A Certificate Manager Agent can change the status, change the
details, reject or approve certificate and revocation requests, revoke certificates,
and approve and configure certificate profiles. The agent’s services interface is
an HTML interface accessible through HTTPS that authenticates agents using
their certificate. The default interface provides all the functionality needed by
agents for a Certificate Manager and is completely customizable.
The agent services interface listens to requests and communicates on the SSL
Agent Services Port. This is the port that the agent goes to in order to access the
agent services interface. The agent services interface is accessible at the
following location:
https://<cms_host_dnsname>:<port_number>
For example:
https://services.example.com:7878
• An End-Entity interface that is accessible by anyone who can access that URL.
The end-entity interface is an HTML interface accessible through either HTTPS
or HTTP (there are two ports set up by default). The default interface provides
forms for the various types of enrollment and other tasks an end entity can
perform and is completely customizable. The end-entity interface listens for
requests on the SSL or Non-SSL End Entity Ports. Both are configured during
installation.
https://<cms_host_dnsname>:<port_number>
For example:
https://services.example.com:7878