HP Secure Key Manager - Manual (Page 232)

data from the client or an error has occurred. When there is no data for a particular field, a dash is
inserted. The format of the Activity Log is as follows:
<date> <priority> <ip> <common name> <user> <request id> <request type> <key> <detail> <error
code> <message>
The following table describes the fields that are present in the Activity Log.
Table 126 Fields in the Activity Log
Field Description
date
enclosed in brackets ( [] ), the date field shows the date and time that the SKM
finished processing the request, specified in the local time zone. The date and time
are represented as follows: yyyy-mm-dd hh:mm:ss.
priority ERROR or INFO, depending on the result of the request
ip IP address of the client machine
common name
enclosed in brackets ( [] ), the common name field displays the common name defined
in the certificate that was provided by the client. This field only has data when you
require client authentication.
user authenticated user that issued the request
request id request ID of the client request
request type
type of client request; the request type field is the name of the XML request without
the suffix “Request.” For example, a KeyGenRequest log entry would have a request
type value of “KeyGen.”
key name of the key specified in the request
detail
enclosed in brackets ( [] ), the detail field provides different information based on the
type of request; the details field is described in Table 127 .
error code numerical error code returned to the client
message
enclosed in brackets ( [] ), the message field displays either “Success” if the server was
able to fulfill the request, or, if there was an error, this field displays the error message
that coincides with the appropriate numerical error code
As mentioned, the detail field provides different information depending on what the client requests.
The following table lists the different types of requests the client might submit and then describes what
information is present in the detail field for each request.
232 Using the Management Console