#2637 Ensuring KRA audit log correctness
Closed: fixed Opened by edewata.

This is part of ticket #2635 phase 1.

The code that generates KRA 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:

  • SECURITY_DATA_ARCHIVAL_REQUEST_PROCESSED
  • SECURITY_DATA_RECOVERY_REQUEST_PROCESSED
  • SECURITY_DATA_RETRIEVE_KEY
  • KEY_STATUS_CHANGE
  • SYMKEY_GENERATION_REQUEST_PROCESSED
  • ASYMKEY_GENERATION_REQUEST_PROCESSED

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1445532

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1445532, https://bugzilla.redhat.com/show_bug.cgi?id=1404075 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1445532)

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1404075, https://bugzilla.redhat.com/show_bug.cgi?id=1445532 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1445532, https://bugzilla.redhat.com/show_bug.cgi?id=1404075)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

Per CS/DS Meeting 09/25/2017: 10.5 blocker

Metadata Update from @mharmsen:
- Issue priority set to: blocker (was: major)

Metadata Update from @vakwetu:
- Issue close_status updated to: fixed

Metadata Update from @vakwetu:
- Issue assigned to vakwetu

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.0 (was: 10.5)

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/2757

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata