Currently the TPS REST operations do not generate audit logs. Additional code needs to be added to each REST method to log the operation.
The REST services need to call PKIService.audit() to generate audit events as defined in ticket #884.
Since REST services can only be used by REST clients, the service code may need to be refactored so that it can be reused directly by other TPS components.
Proposed Milestone: 10.2.2 (per CS Meeting of 09/17/2014)
audit
[PKI TRAC Ticket #1031 - TPS rewrite: add auditing to appropriate places] closed as duplicate of https://fedorahosted.org/pki/ticket/1006 PKI TRAC Ticket #1006 - Audit logging for TPS REST operations (per CS Meeting of 09/17/2014)
Per 10.2.2 Triage meeting of 02/24/2015: 10.2.3
(related to PKI TRAC Ticket #1007 - Additional audit events)
Moving to 10.2.4 per CS team meeting.
Per Dogtag 10.2.x TRIAGE meeting of 04/28/2015: (Tech Preview Feature)
Per CS/DS meeting of 06/08/2015: 10.2.6
Per Dogtag 10.2.6 TRIAGE meeting of 06/30/2015: 10.3
Pushed to master. Sample messages (document) will follow.
commit 41a99a5938c6881a978199fe10b0c392eb27d569 Author: Christina Fu cfu@redhat.com Date: Thu Mar 24 16:23:05 2016 -0700
Ticket #1006 Audit logging for TPS REST operations This patch adds audit logging to TPS REST wrote-specific operations. The read-specific operations are already captured by AuditEvent=AUTHZ_* The affected (new or modified) log messages include: LOGGING_SIGNED_AUDIT_CONFIG_TOKEN_GENERAL_5 LOGGING_SIGNED_AUDIT_CONFIG_TOKEN_PROFILE_6 LOGGING_SIGNED_AUDIT_CONFIG_TOKEN_MAPPING_RESOLVER_6 LOGGING_SIGNED_AUDIT_CONFIG_TOKEN_AUTHENTICATOR_6 LOGGING_SIGNED_AUDIT_CONFIG_TOKEN_CONNECTOR_6 LOGGING_SIGNED_AUDIT_CONFIG_TOKEN_RECORD_6 LOGGING_SIGNED_AUDIT_TOKEN_STATE_CHANGE_8
Metadata Update from @edewata: - Issue assigned to cfu - Issue set to the milestone: 10.3.0.b1
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1572
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.