Netscape MANAGEMENT SYSTEM 4.5 - AGENT GUIDE Manual page 30

Managing Requests
Process the request (see "Approving Requests" on page 35 and "Other Options
3.
for Handling Requests" on page 43).
In processing a request for a certificate, you can choose to take one of the
following actions:
Each of these actions changes the status of the certificate request. If you close
the form without taking one of these actions, the request remains in the queue
with the same status.
It's also possible to clone any request, whether it's still pending, canceled,
rejected, or completed. This can be useful in a variety of situations. For
example, if a user receives a certificate that doesn't work because it has been
incorrectly formulated, you can locate the completed request, clone it, and
correct it without requiring the user to enroll a second time. Cloning a request
gives it a new request ID number and puts it into the list of pending requests,
but does not change the status of the original request.
Figure 2-1 illustrates the process for handling requests and the different types
of status for a request.
30 Netscape Certificate Management System Agent's Guide • October 2001
Approve the request. You can approve a request manually, or it can be
approved automatically by policy modules if the request has been
authenticated by an authentication module (and if the CMS administrator
has configured the system to do this). After a request has been approved,
Certificate Management System issues the requested certificate (Certificate
Manager) or passes it on to the Certificate Manager for issuance
(Registration Manager).
Reject the request. You can reject a request manually, or it can be rejected
automatically by a policy module if it does not conform to your
organization's policies. If the CMS administrator has configured the
system to provide automatic notifications to end users, a rejected request
will automatically result in such a notification being sent.
Cancel the request. You can cancel a request manually, but requests are
never cancelled automatically, and users do not receive automatic
notification of cancelled requests. Cancellation can be useful, for example,
if the user has left the company since submitting the request, or if you have
already talked to the user over the phone about the problem and therefore
don't need to invoke automatic notification.