Configuring Tps Audit Logs In The Admin Services Page - Red Hat CERTIFICATE SYSTEM 8.0 - ADMINISTRATION Admin Manual

Chapter 15. Configuring Subsystem Logs
2. The Log Event Listener Management tab lists the currently configured listeners.
To create a new log instance, click Add, and select a module plug-in from the list in the Select
Log Event Listener Plug-in Implementation window.
3. Set or modify the fields in the Log Event Listener Editor window. The different parameters are
Table 15.5, "Log Event Listener
listed in
Field
Log Event Listener ID
type
enabled
level
fileName
bufferSize
flushInterval
maxFileSize
rolloverInterval
Table 15.5. Log Event Listener Fields

15.3.2. Configuring TPS Audit Logs in the Admin Services Page

The TPS's audit log records specific system events that are related to both TPS subsystem events
like startup and token management events like formatting a smart card. At the least, a note of these
activities is recorded; for some activities verbose messages are recorded.
NOTE
The TPS debug and error logs cannot be configured through the admin services page;
these must be configured directly in the CS.cfg file, as described in
"Configuring TPS
There are two locations for the audit logs. Regular audit logs are in /var/log/subsystem_name/
tps-audit.log. If signed audit logging is enabled, then the signed audit log is written to /var/
log/subsystem_name/signedAudit/tps-audit.log.
The are two parts for enabling audit logging. The first is enabling the audit log itself, using the Enable|
Disable radio buttons. The second part is enabling signed audit logging. This signs the audit log after
every entry with a special signing certificate as a sign that the log has not been tampered with.
After enabling logging, then administrators can set what operations are recorded in the audit log.
368
Fields".
Description
The unique name that identifies the listener. The names can have any combination of lette
(_), and a hyphen (-), but it cannot contain other characters or spaces.
The type of log file. system creates error and system logs; transaction records audit logs
Sets whether the log is active. Only enabled logs actually record events. The value is eith
Sets the log level in the text field. The level must be manually entered in the field; there is
Debug, Information, Warning, Failure, Misconfiguration, Catastrophe, and Security.
"Log Levels (Message
The full path, including the filename, to the log file. The subsystem user should have read
The buffer size in kilobytes (KB) for the log. Once the buffer reaches this size, the content
to the log file. The default size is 512 KB. For more information on buffered logging, see
Logging".
The amount of time before the contents of the buffer are flushed out and added to the log
The size, kilobytes (KB), a log file can become before it is rotated. Once it reaches this siz
log file is started new. For more information on log file rotation, see
The frequency which the server rotates the active log file. The available choices are hourl
default selection is monthly. For more information, see
Logging".
Categories)".
Section 15.4.3,
Section 15.1.4, "Log F
Section 15.1.4, "Log File Rotation"
S