This is part of ticket #2635 phase 1.
The code that generates common (not subsystem-specific) audit log need to be inspected to ensure that it includes the correct audit fields. This can be done by creating strongly-typed event class as described in the following page:
http://pki.fedoraproject.org/wiki/PKI_10.4_Audit_Log_Improvements
Metadata Update from @edewata: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
This includes the following audit events:
Patches for review:
Metadata Update from @edewata: - Issue assigned to edewata
This is documented in the following page: http://pki.fedoraproject.org/wiki/PKI_Server_Audit_Events
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.5 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1452340
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27
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/2761
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.